-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error cause is not logged in dev:watch mode #2533
Labels
Comments
Would you like to create a PR for this issue? |
I guess we can close this in favor of evanw/node-source-map-support#337 But I don't think they would fix that soon |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current behavior
I change tsconfig.json target to ES2022
I throw an error in onModuleInit in a service:
I run:
nest start --watch
In the terminal I see that the cause is not logged:
When I run
nest build
and thennode dist/main
, I have the expected stack trace:Minimum reproduction code
https://github.com/dmitryrn/nestrepro
Steps to reproduce
clone the reproduction code;
run
npm run start:dev
;see that error's cause is not logged;
run
npm run build && npm run start:prod
;see that error's cause is logged.
Expected behavior
Seeing an error cause while in
nest start --watch
modePackage
@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.0.0
Packages versions
Node.js version
v21.6.2
In which operating systems have you tested?
Other
While I was creating a reproduction repo, I realized that since you have ES2021 in your default tsconfig.json, that means you don't have to support ES2022. But still it would be nice to have error's cause to be logged.
The text was updated successfully, but these errors were encountered: