-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[NESTJS] Please add support to NestJS 11 #15110
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
Comments
Hi @samuelexferri, thanks for filing this. We'll definitely want to support this, I added it to our backlog and will discuss with the team. |
This depends partly on #13674 as NestJS v11 uses Express v5 out of the box. We might be able to ship a version with limited support for now though |
People searching for an intermediate solution: Add the following to the end of your package.json to enforce the new version:
Be aware that this still does not guarantee everything works as expected |
Closing this because the PR to add Nest.js support is merged: #15114 Please keep in mind that the support is limited right now, as certain spans regarding Express 5 are missing. However, as soon as Express 5 is supported by Sentry, everything is going to work as usual. This will be released with the next version of v9. |
I have a question, the issue was solved in the new versions of Sentry 9? |
Yes, it's added in 8.51.0 and 9.1.0 |
Problem Statement
Please add support to NestJS 11
Solution Brainstorm
The text was updated successfully, but these errors were encountered: