Cannot find package 'output/server/node_modules/@sentry/node/node_modules/@opentelemetry/instrumentation/index.js' imported from .output/server/node_modules/@sentry/node/build/esm/otel/instrument.js

[fristys]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nuxt

SDK Version

9.30.0

Framework Version

Nuxt 3.17.1

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

1. Stub out a regular Nuxt app with @sentry/nuxt
2. Configure it to use autoInjectServerSentry: 'top-level-import'
3. Build
4. Run the production server from .output

Expected Result

For the server to work and not crash.

Actual Result

2025-06-18T05:26:56.0442399Z 05:26:56 1| | You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
2025-06-18T05:26:56.0453372Z 05:26:56 1| | Error: Cannot find package '/home/site/wwwroot/.output/server/node_modules/@sentry/node/node_modules/@opentelemetry/instrumentation/index.js' imported from /home/site/wwwroot/.output/server/node_modules/@sentry/node/build/esm/otel/instrument.js
2025-06-18T05:26:56.0455227Z 05:26:56 1| | Did you mean to import "@opentelemetry/instrumentation/build/src/index.js"?
2025-06-18T05:26:56.0459206Z 05:26:56 1| |     at legacyMainResolve (node:internal/modules/esm/resolve:215:26)
2025-06-18T05:26:56.0459387Z 05:26:56 1| |     at packageResolve (node:internal/modules/esm/resolve:860:14)
2025-06-18T05:26:56.0459463Z 05:26:56 1| |     at moduleResolve (node:internal/modules/esm/resolve:946:18)
2025-06-18T05:26:56.0467544Z 05:26:56 1| |     at defaultResolve (node:internal/modules/esm/resolve:1188:11)
2025-06-18T05:26:56.0467703Z 05:26:56 1| |     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)
2025-06-18T05:26:56.0467767Z 05:26:56 1| |     at ModuleLoader.#cachedDefaultResolve (node:internal/modules/esm/loader:591:25)
2025-06-18T05:26:56.0467822Z 05:26:56 1| |     at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38)
2025-06-18T05:26:56.0467892Z 05:26:56 1| |     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38)
2025-06-18T05:26:56.0467944Z 05:26:56 1| |     at ModuleJob._link (node:internal/modules/esm/module_job:130:49)
2025-06-18T05:26:56.0595506Z 05:26:56 0| | You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
2025-06-18T05:26:56.0596122Z 05:26:56 0| | Error: Cannot find package '/home/site/wwwroot/.output/server/node_modules/@sentry/node/node_modules/@opentelemetry/instrumentation/index.js' imported from /home/site/wwwroot/.output/server/node_modules/@sentry/node/build/esm/otel/instrument.js
2025-06-18T05:26:56.059623Z 05:26:56 0| | Did you mean to import "@opentelemetry/instrumentation/build/src/index.js"?
2025-06-18T05:26:56.0596287Z 05:26:56 0| |     at legacyMainResolve (node:internal/modules/esm/resolve:215:26)
2025-06-18T05:26:56.0596338Z 05:26:56 0| |     at packageResolve (node:internal/modules/esm/resolve:860:14)
2025-06-18T05:26:56.0596404Z 05:26:56 0| |     at moduleResolve (node:internal/modules/esm/resolve:946:18)
2025-06-18T05:26:56.0596453Z 05:26:56 0| |     at defaultResolve (node:internal/modules/esm/resolve:1188:11)
2025-06-18T05:26:56.0596503Z 05:26:56 0 |     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)
2025-06-18T05:26:56.0596556Z 05:26:56 0| |     at ModuleLoader.#cachedDefaultResolve (node:internal/modules/esm/loader:591:25)
2025-06-18T05:26:56.0596633Z 05:26:56 0| |     at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38)
2025-06-18T05:26:56.0596691Z 05:26:56 0| |     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38)
2025-06-18T05:26:56.0596746Z 05:26:56 0| |     at ModuleJob._link (node:internal/modules/esm/module_job:130:49)

[andreiborza]

Hi @fristys, I tried this in a new nuxt project and didn't run into it.

Could you share a bit more about your setup, which package manager are you using? A reproduction repo would also help in resolving this.

[fristys]

Hi @fristys, I tried this in a new nuxt project and didn't run into it.

Could you share a bit more about your setup, which package manager are you using? A reproduction repo would also help in resolving this.

• We're using plain old NPM (the lockfile was generated on Node v22.x / NPM 11.4.x but that doesn't seem to change anything)
• We build via Azure pipelines (Node 20.x)
• We deploy to a Linux Azure service (again Node 20.x) that runs the production server via PM2.

Unfortunately, I can't really share any of our code for repro since I'm not allowed to (customer project), but as soon as we remove @sentry/nuxt from our nuxt.config file's modules things start working again as expected.

If we leave it there, but set sentry: { enabled: false } the server no longer crashes on init and Nuxt launches, but we get 500 with the same error body as my original post for every route navigation.

If I inspect the module folders it's complaining about in the resulting pipeline artifact, I can indeed see that the file it's trying to import does not exist, but it also doesn't exist on the live opentelemetry package. Could something have changed somewhere in the dependencies recently that breaks it?

Here's a partial version of our nuxt.config in case that's relevant:

sourcemap: {
     client: isProduction ? 'hidden' : undefined
},

experimental: {
     sharedPrerenderData: true
},

sentry: {
    enabled: isProduction,
     autoInjectServerSentry: 'top-level-import',

     sourceMapsUploadOptions: {
        enabled: !!process.env.CI,
        org: '',
        project: '',
         telemetry: false,
         silent: !process.env.CI
     }
 }

[andreiborza]

Could you please run and paste the output of

npm ls @opentelemetry/instrumentation

[fristys]

Could you please run and paste the output of

npm ls @opentelemetry/instrumentation

Certainly:

└─┬ @sentry/nuxt@9.30.0
  ├─┬ @sentry/node@9.30.0
  │ ├─┬ @opentelemetry/instrumentation-amqplib@0.46.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-connect@0.43.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-dataloader@0.16.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-express@0.47.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-fs@0.19.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-generic-pool@0.43.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-graphql@0.47.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-hapi@0.45.2
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-http@0.57.2
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-ioredis@0.47.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-kafkajs@0.7.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-knex@0.44.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-koa@0.47.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-lru-memoizer@0.44.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-mongodb@0.52.0
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-mongoose@0.46.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-mysql@0.45.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-mysql2@0.45.2
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-pg@0.51.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-redis-4@0.46.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-tedious@0.18.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├─┬ @opentelemetry/instrumentation-undici@0.10.1
  │ │ └── @opentelemetry/instrumentation@0.57.2
  │ ├── @opentelemetry/instrumentation@0.57.2
  │ └─┬ @prisma/instrumentation@6.8.2
  │   └── @opentelemetry/instrumentation@0.57.2
  └─┬ @sentry/opentelemetry@9.30.0
    └── @opentelemetry/instrumentation@0.200.0