`@sentry/nuxt` is not included in the build output `node_modules`

[s1gr1d]

This is not really a bug, but it might cause problems. This issue just helps get up-to-date on the behavior as this was already investigated.

After some testing, the PR creating this change was found: nuxt/nuxt#30136

With this PR, the directory that is added to node_modules is [...dir]/node_modules/@sentry/nuxt and not @sentry/nuxt/module anymore. This probably leads to resolving and inlining the @sentry/nuxt dependency.

---

Description

Ideally, the sentry.server.config.mjs file in the build output should look like this (before Nuxt v3.15.0 with npm):

import process from 'node:process';
// debug ID code
import * as Sentry from '@sentry/nuxt';
import './chunks/virtual/_sentry-release-injection-file.mjs';

Sentry.init({
  dsn: "https://dsn.url",
  tracesSampleRate: 1,
});
//# sourceMappingURL=sentry.server.config.mjs.map

However, after Nuxt version 3.15.0, @sentry/nuxt is not is not included in the node_modules in the build output folder. The dependency is inlined with imports from @sentry/node and @sentry/core. This is fine, but kept in mind when putting libraries into Rollup externals.

After nightly 3.15.0-28892109.0e84cb9a (which corresponds to this commit) the dependency @sentry/nuxt is not added anymore.

It could be another commit as well - between those two nightlies are several commits:

  '3.15.0-28890210.3b129290' --> adds dependency
  '3.15.0-28892109.0e84cb9a' --> does not add it

[linear]

JS-792 `@sentry/nuxt` is not included in the build output `node_modules`

[s1gr1d]

Will close this as this is no bug, but we can keep it as a reference.