`@sentry-internal/nitro-utils` import warning

[Gregoire-Fremaux]

Environment

SaaS (https://sentry.io/)

What are you trying to accomplish?

Hello, in my Nuxt 3 Sentry integration, the frontend part works correctly, but on the backend side, which uses Nitro, Sentry is looking for a module that doesn't seem to be public in the yarn packages.

Is this intentional?

How are you getting stuck?

[8:53:23 AM]  WARN  "@sentry-internal/nitro-utils" is imported by "node_modules/@sentry/nuxt/build/module/runtime/plugins/sentry.server.js", but could not be resolved – treating it as an external dependency.

Cannot find any modules named @sentry-internal/nitro-utils on npm or yarn

Where in the product are you?

Issues

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[s1gr1d]

It's failing on this warning as it is wrongfully detecting the package as external but it is not external.

Currently, you can only downgrade to 8.42.0. I disabled "fail on warn" in this PR and this is going to be released soon.

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #14662, which was included in the 8.44.0 release.

[phooijenga]

I'm still having this issue with 8.44.0:

node:internal/modules/esm/resolve:838
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@sentry-internal/nitro-utils' imported from /Users/paul/.../.output/server/index.mjs
    at packageResolve (node:internal/modules/esm/resolve:838:9)
    at moduleResolve (node:internal/modules/esm/resolve:907:18)
    at defaultResolve (node:internal/modules/esm/resolve:1037:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:650:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:599:25)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:582:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:241:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:132:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Downgrading to 8.42.0 works.