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
Reacted by Alexander Bykhov, Daniel Höflehner, Nick Hall, Julian Zatloukal, BILAL M SHATARA, Peter Gledhill, Chris Cremeans, Rudyard Murdough, Mads Hougesen, Senne Dirkx and 9 more
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.
Reacted by Mads Hougesen, Samuele Ferri and Neil Poulin
Activity
andreiborza commentedon Jan 21, 2025
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.
chargome commentedon Jan 22, 2025
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
Agreon commentedon Feb 6, 2025
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
s1gr1d commentedon Feb 11, 2025
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.
thgemanuel commentedon Mar 19, 2025
I have a question, the issue was solved in the new versions of Sentry 9?
s1gr1d commentedon Mar 19, 2025
Yes, it's added in 8.51.0 and 9.1.0