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
This updates nuxt build logs a bit:
1. Make sure everything is gated behind `debug: true`
2. Show short message when sourceMaps: false without `debug: true`
3. Adjust messages to align with other SDKs a bit more.
4. Avoid `consoleSandbox` which we do not need there
'[Sentry] Set `sourcemapExcludeSources: false` in the Nuxt config (`nitro.rollupConfig.output`). Source maps will now include the actual code to be able to un-minify code snippets in Sentry.',
375
-
);
376
-
});
363
+
// eslint-disable-next-line no-console
364
+
console.log(
365
+
'[Sentry] Set `sourcemapExcludeSources: false` in the Nuxt config (`nitro.rollupConfig.output`). Source maps will now include the actual code to be able to un-minify code snippets in Sentry.',
366
+
);
377
367
}
378
368
}
379
369
@@ -389,12 +379,10 @@ function validateDifferentSourceMapSettings({
389
379
otherSettingValue?: SourceMapSetting;
390
380
}): void{
391
381
if(nuxtSettingValue!==otherSettingValue){
392
-
consoleSandbox(()=>{
393
-
// eslint-disable-next-line no-console
394
-
console.warn(
395
-
`[Sentry] Source map generation settings are conflicting. Sentry uses \`${nuxtSettingKey}: ${nuxtSettingValue}\`. However, a conflicting setting was discovered (\`${otherSettingKey}: ${otherSettingValue}\`). This setting was probably explicitly set in your configuration. Sentry won't override this setting but it may affect source maps generation and upload. Without source maps, code snippets on the Sentry Issues page will remain minified.`,
396
-
);
397
-
});
382
+
// eslint-disable-next-line no-console
383
+
console.warn(
384
+
`[Sentry] Source map generation settings are conflicting. Sentry uses \`${nuxtSettingKey}: ${nuxtSettingValue}\`. However, a conflicting setting was discovered (\`${otherSettingKey}: ${otherSettingValue}\`). This setting was probably explicitly set in your configuration. Sentry won't override this setting but it may affect source maps generation and upload. Without source maps, code snippets on the Sentry Issues page will remain minified.`,
385
+
);
398
386
}
399
387
}
400
388
@@ -404,27 +392,26 @@ function logKeepEnabledSourceMapSetting(
404
392
settingValue: string,
405
393
): void{
406
394
if(sentryNuxtModuleOptions.debug){
407
-
consoleSandbox(()=>{
408
-
// eslint-disable-next-line no-console
409
-
console.log(
410
-
`[Sentry] \`${settingKey}\` is enabled with \`${settingValue}\`. This will correctly un-minify the code snippet on the Sentry Issue Details page.`,
411
-
);
412
-
});
395
+
// eslint-disable-next-line no-console
396
+
console.log(
397
+
`[Sentry] \`${settingKey}\` is enabled with \`${settingValue}\`. This will correctly un-minify the code snippet on the Sentry Issue Details page.`,
`[Sentry] We discovered \`${settingKey}\` is set to \`false\`. This setting is either a default setting or was explicitly set in your configuration. Sentry won't override this setting. Without source maps, code snippets on the Sentry Issues page will remain minified. To show unminified code, enable source maps in \`${settingKey}\` (e.g. by setting them to \`'hidden'\`).`,
406
+
`[Sentry] Source map generation is currently disabled in your Vite configuration (\`${settingKey}: false \`). This setting is either a default setting or was explicitly set in your configuration. Sentry won't override this setting. Without source maps, code snippets on the Sentry Issues page will remain minified. To show unminified code, enable source maps in \`${settingKey}\` (e.g. by setting them to \`hidden\`).`,
421
407
);
422
-
});
408
+
}else{
409
+
// eslint-disable-next-line no-console
410
+
console.warn(`[Sentry] Source map generation (\`${settingKey}\`) is disabled in your Vite configuration.`);
0 commit comments