feat(astro): Deprecate passing runtime config to astro integration#16839
feat(astro): Deprecate passing runtime config to astro integration#16839
Conversation
There was a problem hiding this comment.
Bug: Sentry Vite Plugin Ignores Astro's `excludeTracing`
The excludePerformanceMonitoring mapping for options.bundleSizeOptimizations?.excludeTracing was prematurely removed from the Sentry Vite plugin configuration. This mapping translated the Astro integration's excludeTracing option to the Vite plugin's excludePerformanceMonitoring option. Its removal, intended for a future Vite plugin version (v2.22.0) not yet guaranteed, causes the excludeTracing option to be ignored, breaking bundle size optimizations for users who rely on it to exclude performance monitoring.
packages/astro/src/integration/index.ts#L104-L108
sentry-javascript/packages/astro/src/integration/index.ts
Lines 104 to 108 in 9c4b98c
Was this report helpful? Give feedback by reacting with 👍 or 👎
…etsentry#16839) Closes getsentry#16837 This should not break anything, I actually added a test to verify injecting this works as expected. We now simply console.warn when some runtime config is passed in the astro integration. Also, no more type completion exists for these, but they are still accepted via `Record<string, unknown>`.
Closes #16837
This should not break anything, I actually added a test to verify injecting this works as expected. We now simply console.warn when some runtime config is passed in the astro integration. Also, no more type completion exists for these, but they are still accepted via
Record<string, unknown>.