-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
sentrySvelteKit
loads Vite config in the wrong mode
#15414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @giacomoran thanks for reporting! Hmm yeah this looks like a consequence of #14886 (damn, never thought this change would be so problematic). We need to check if we can detect the mode dynamically. Otherwise I'm afraid we need to re-think our approach. I'll take a look. |
Quick update: We decided to rework the source map setting extraction logic to use Vite's provided
This should be released in the next days. |
A PR closing this issue has just been released 🚀This issue was referenced by PR #15440, which was included in the 9.2.0 release. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/sveltekit
SDK Version
9.1.0
Framework Version
2.16.0
Link to Sentry event
No response
Reproduction Example/SDK Setup
https://github.com/giacomoran/sveltekit-sentry-vite-config
Steps to Reproduce
@sentry/sveltekit
as dependencysentrySvelteKit
plugin to Vite configvite build --mode staging
Expected Result
Every time the Vite config is loaded, the mode is
staging
.Actual Result
When the
sentrySvelteKit
plugin loads the Vite config, the mode isproduction
instead ofstaging
.Example output:
The text was updated successfully, but these errors were encountered: