You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using INestApplicationContext.select to select a module that is NOT loaded in the app an error is thrown (Nest could not select the given module (it does not exist in current context)).
But this error is not caught by try/catch, preventing us to handle the error manually, resulting in crashing the app.
You can see in the stackblitz provided that the console.log located in the main.ts is not triggered when a module is not found.
I have discussed this on discord, and we concluded it might be a bug.
I didn't know about abortOnError.
But I would like to keep the abortOnError behavior for the all the other errors.
It's just when selecting a non existing module that I would like to be able to catch and handle the error myself.
To be clear, this problem is not blocking for me (I found some workarounds) but I thought there might be an issue with the select that's why I created this issue.
In my opinion it would be nice to have this behavior, but I let you see if you want to change it or not.
I don't know if it's worth it.
Is there an existing issue for this?
Current behavior
When using
INestApplicationContext.select
to select a module that is NOT loaded in the app an error is thrown (Nest could not select the given module (it does not exist in current context)
).But this error is not caught by try/catch, preventing us to handle the error manually, resulting in crashing the app.
You can see in the stackblitz provided that the
console.log
located in the main.ts is not triggered when a module is not found.I have discussed this on discord, and we concluded it might be a bug.
Minimum reproduction code
https://stackblitz.com/edit/nestjs-starter-rgdzro?file=src%2Fmain.ts
Steps to reproduce
In your main.ts:
Or just run the stackblitz provided.
Expected behavior
I expect the error thrown by the select to be caught by the try/catch.
Package
@nestjs/common
@nestjs/core
@nestjs/microservices
@nestjs/platform-express
@nestjs/platform-fastify
@nestjs/platform-socket.io
@nestjs/platform-ws
@nestjs/testing
@nestjs/websockets
Other package
No response
NestJS version
10.2.10
Packages versions
@nestjs/10.2.10
Node.js version
18.16.0
In which operating systems have you tested?
Other
No response
The text was updated successfully, but these errors were encountered: