Skip to content

[NESTJS] Please add support to NestJS 11 #15110

Closed

Description

@samuelexferri

Problem Statement

Please add support to NestJS 11

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sentry/nestjs@8.50.0
npm error Found: @nestjs/common@11.0.3
npm error node_modules/@nestjs/common
npm error   @nestjs/common@"^11.0.3" from the root project
npm error   peer @nestjs/common@"^9.0.0 || ^10.0.0 || ^11.0.0" from @nestjs/cache-manager@3.0.0
npm error   node_modules/@nestjs/cache-manager
npm error     @nestjs/cache-manager@"^3.0.0" from the root project
npm error   14 more (@nestjs/config, @nestjs/core, @nestjs/jwt, ...)
npm error
npm error Could not resolve dependency:
npm error peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @sentry/nestjs@8.50.0
npm error node_modules/@sentry/nestjs
npm error   @sentry/nestjs@"^8.50.0" from the root project
npm error
npm error Conflicting peer dependency: @nestjs/common@10.4.15
npm error node_modules/@nestjs/common
npm error   peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @sentry/nestjs@8.50.0
npm error   node_modules/@sentry/nestjs
npm error     @sentry/nestjs@"^8.50.0" from the root project

Solution Brainstorm

"peerDependencies": {
   "@nestjs/common": "^8.0.0 || ^9.0.0 || ^10.0.0" || ^11.0.0",
   "@nestjs/core": "^8.0.0 || ^9.0.0 || ^10.0.0" || ^11.0.0"
 },

Activity

  1. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Jan 21, 2025
  2. andreiborza commented on Jan 21, 2025

    @andreiborza
    Member

    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.

  3. self-assigned this
    on Jan 21, 2025
  4. chargome commented on Jan 22, 2025

    @chargome
    Member

    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

  5. self-assigned this
    on Feb 5, 2025
  6. Agreon commented on Feb 6, 2025

    @Agreon

    People searching for an intermediate solution: Add the following to the end of your package.json to enforce the new version:

     "overrides": {
        "@nestjs/common": "^11.0.8",
        "@nestjs/core": "^11.0.8"
      }
    

    Be aware that this still does not guarantee everything works as expected

  7. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on Feb 6, 2025
  8. s1gr1d commented on Feb 11, 2025

    @s1gr1d
    Member

    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.

  9. thgemanuel commented on Mar 19, 2025

    @thgemanuel

    I have a question, the issue was solved in the new versions of Sentry 9?

  10. s1gr1d commented on Mar 19, 2025

    @s1gr1d
    Member

    Yes, it's added in 8.51.0 and 9.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions