getsentry / getsentry/sentry-javascript

`project` option type should be `string | string[]` across all framework SDKs

未关闭
#21,069 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
TypeScript
星标
8.7k
派生
1.8k
平均合并
1 天 17 小时
30 天内合并 PR
515

描述

`@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.

[https://github.com/getsentry/sentry-javascript/pull/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:66`
* `packages/nuxt/src/common/types.ts:118`
* `packages/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.

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。