You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// We don't need to check for AUTH_TOKEN here, because the plugin will pick it up from the env
37
37
if(shouldUploadSourcemaps&&command!=='dev'){
38
+
// TODO(v9): Remove this warning
39
+
if(config?.vite?.build?.sourcemap===false){
40
+
logger.warn(
41
+
"You disabled sourcemaps with the `vite.build.sourcemap` option. Currently, the Sentry SDK will override this option to generate sourcemaps. In future versions, the Sentry SDK will not override the `vite.build.sourcemap` option if you explicitly disable it. If you want to generate and upload sourcemaps please set the `vite.build.sourcemap` option to 'hidden' or undefined.",
42
+
);
43
+
}
44
+
45
+
// TODO: Add deleteSourcemapsAfterUpload option and warn if it isn't set.
`[@sentry/nextjs - ${runtimePrefix}] You disabled sourcemaps with the Webpack \`devtool\` option. Currently, the Sentry SDK will override this option to generate sourcemaps. In future versions, the Sentry SDK will not override the \`devtool\` option if you explicitly disable it. If you want to generate and upload sourcemaps please set the \`devtool\` option to 'hidden-source-map' or undefined.`,
345
+
);
346
+
}
347
+
348
+
// TODO(v9): Remove this warning and print warning in case source map deletion is auto configured
"[@sentry/nextjs] The Sentry SDK has enabled source map generation for your Next.js app. If you don't want to serve Source Maps to your users, either set the `deleteSourceMapsAfterUpload` option to true, or manually delete the source maps after the build. In future Sentry SDK versions `deleteSourceMapsAfterUpload` will default to `true`.",
353
+
);
354
+
}
355
+
339
356
// `hidden-source-map` produces the same sourcemaps as `source-map`, but doesn't include the `sourceMappingURL`
340
357
// comment at the bottom. For folks who aren't publicly hosting their sourcemaps, this is helpful because then
341
358
// the browser won't look for them and throw errors into the console when it can't find them. Because this is a
342
359
// front-end-only problem, and because `sentry-cli` handles sourcemaps more reliably with the comment than
343
360
// without, the option to use `hidden-source-map` only applies to the client-side build.
`[Sentry SolidStart PLugin] We recommend setting the \`sourceMapsUploadOptions.filesToDeleteAfterUpload\` option to clean up source maps after uploading.
26
-
[Sentry SolidStart Plugin] Otherwise, source maps might be deployed to production, depending on your configuration`,
27
-
);
28
-
}
21
+
console.warn(
22
+
"[Sentry SolidStart Plugin] You disabled sourcemaps with the `build.sourcemap` option. Currently, the Sentry SDK will override this option to generate sourcemaps. In future versions, the Sentry SDK will not override the `build.sourcemap` option if you explicitly disable it. If you want to generate and upload sourcemaps please set the `build.sourcemap` option to 'hidden' or undefined.",
23
+
);
29
24
}
25
+
26
+
// TODO(v9): Remove this warning and print warning in case source map deletion is auto configured
"[Sentry SolidStart Plugin] The Sentry SDK has enabled source map generation for your SolidStart app. If you don't want to serve Source Maps to your users, either configure the `filesToDeleteAfterUpload` option with a glob to remove source maps after uploading them, or manually delete the source maps after the build. In future Sentry SDK versions source maps will be deleted automatically after uploading them.",
0 commit comments