Add local dev Sentry DSN support and fix environment tag for test vs. production
Continuous Integration / config (pull_request) Successful in 9s
Continuous Integration / prepare (pull_request) Successful in 1m13s
Continuous Integration / build (pull_request) Successful in 1m57s
Continuous Integration / test (pull_request) Successful in 1m47s
Continuous Integration / deploy-test (pull_request) Skipped

Co-authored-by: Junie <junie@jetbrains.com>
This commit is contained in:
2026-07-25 14:55:06 +02:00
co-authored by Junie
parent 1207bc1453
commit b7617d968d
4 changed files with 40 additions and 2 deletions
+4 -1
View File
@@ -10,7 +10,10 @@ const sentryDsn = import.meta.env.VITE_SENTRY_DSN;
if (sentryDsn) {
Sentry.init({
dsn: sentryDsn,
environment: import.meta.env.MODE,
// VITE_APP_ENV ('test' | 'production') distinguishes test vs. production builds — both use
// `vite build` without an explicit mode, so MODE alone would tag both as 'production'.
// Falls back to MODE for local development (`pnpm dev` -> 'development').
environment: import.meta.env.VITE_APP_ENV ?? import.meta.env.MODE,
release: __APP_VERSION__,
integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
// Low-traffic marketing site: capture all traces (lower this if traffic grows significantly).