@sentry/node@11.1.0 lists @sentry/bundler-plugins in dependencies, although only the optional @sentry/node/{vite,rollup,webpack,esbuild} entry points use it; the main entry never loads it. For apps that only use the main entry, every production install therefore gets bundler-plugins and its dependencies: the sentry CLI, a native oxc-parser binary, magic-string, dotenv. pnpm also links the optional rollup peer to whatever rollup the workspace has, which produces unmet peer rollup@">=3.2.0" warnings. Removing the package with an override has no effect on the SDK. Could it be an optional peer dependency, or live in a separate package?
@sentry/node@11.1.0lists@sentry/bundler-pluginsindependencies, although only the optional@sentry/node/{vite,rollup,webpack,esbuild}entry points use it; the main entry never loads it. For apps that only use the main entry, every production install therefore gets bundler-plugins and its dependencies: thesentryCLI, a nativeoxc-parserbinary,magic-string,dotenv. pnpm also links the optionalrolluppeer to whatever rollup the workspace has, which producesunmet peer rollup@">=3.2.0"warnings. Removing the package with an override has no effect on the SDK. Could it be an optional peer dependency, or live in a separate package?