README states that NestJS v7 is supported, however this is now quite an old version.
Is it possible to clarify support for newer versions of NestJS?
I'm currently experiencing an issue since updating from NestJS 7 -> 8 and node 14 -> 18, and I think it might be caused by lambda-request-handler, which relies on in-process-request.
Specifically, I'm getting this exception:
TypeError [ERR_INVALID_ARG_TYPE]: The "stream" argument must be an instance of ReadableStream, WritableStream, or Stream. Received an instance of Object
at new NodeError (node:internal/errors:405:5)
at eos (node:internal/streams/end-of-stream:74:11)
at IncomingMessage._destroy (node:_http_incoming:234:21)
at _destroy (node:internal/streams/destroy:109:10)
at IncomingMessage.destroy (node:internal/streams/destroy:71:5)
at endReadableNT (node:internal/streams/readable:1416:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'ERR_INVALID_ARG_TYPE'
}
Given the stack trace is all for internal node modules, I can't be sure what is triggering it, so this might be unrelated to in-process-request, but given it doesn't explicitly support NestJS 8, it seemed worth investigating.
README states that NestJS v7 is supported, however this is now quite an old version.
Is it possible to clarify support for newer versions of NestJS?
I'm currently experiencing an issue since updating from NestJS 7 -> 8 and node 14 -> 18, and I think it might be caused by lambda-request-handler, which relies on in-process-request.
Specifically, I'm getting this exception:
Given the stack trace is all for internal node modules, I can't be sure what is triggering it, so this might be unrelated to in-process-request, but given it doesn't explicitly support NestJS 8, it seemed worth investigating.