@sentry/bundler-plugin-core accepts string | string[] for the project option, but our SDK types narrow it to string, causing a TypeScript error when users pass an array.
#21067 fixes this for Next.js. The same mismatch exists in:
Top-level options:
packages/core/src/build-time-plugins/buildTimeOptionsBase.ts:40 (root cause — inherited by nuxt, sveltekit, astro)packages/solidstart/src/vite/types.ts:111 (standalone definition)
Deprecated sourceMapsUploadOptions.project:
packages/astro/src/integration/types.ts:66packages/nuxt/src/common/types.ts:118packages/sveltekit/src/vite/types.ts:42
These deprecated options are still live code paths — each SDK falls back to them via topLevel.project ?? sourceMapsUploadOptions.project ?? env, so users who haven't migrated hit the same TS error.
All locations forward project verbatim to the bundler plugin, so the fix is type-only: widen to string | string[] in each location.
@sentry/bundler-plugin-coreacceptsstring | string[]for theprojectoption, but our SDK types narrow it tostring, causing a TypeScript error when users pass an array.#21067 fixes this for Next.js. The same mismatch exists in:
Top-level options:
packages/core/src/build-time-plugins/buildTimeOptionsBase.ts:40(root cause — inherited by nuxt, sveltekit, astro)packages/solidstart/src/vite/types.ts:111(standalone definition)Deprecated
sourceMapsUploadOptions.project:packages/astro/src/integration/types.ts:66packages/nuxt/src/common/types.ts:118packages/sveltekit/src/vite/types.ts:42These deprecated options are still live code paths — each SDK falls back to them via
topLevel.project ?? sourceMapsUploadOptions.project ?? env, so users who haven't migrated hit the same TS error.All locations forward
projectverbatim to the bundler plugin, so the fix is type-only: widen tostring | string[]in each location.