ci: add verification workflow
This commit is contained in:
@@ -41,6 +41,9 @@ const nextConfig: NextConfig = {
|
||||
},
|
||||
};
|
||||
|
||||
const shouldUploadSentrySourcemaps =
|
||||
process.env.CI !== "true" || process.env.SENTRY_UPLOAD_SOURCEMAPS === "1";
|
||||
|
||||
export default withSentryConfig(withSerwist(nextConfig), {
|
||||
// For all available options, see:
|
||||
// https://www.npmjs.com/package/@sentry/webpack-plugin#options
|
||||
@@ -52,12 +55,21 @@ export default withSentryConfig(withSerwist(nextConfig), {
|
||||
// Only print logs for uploading source maps in CI
|
||||
silent: !process.env.CI,
|
||||
|
||||
// Keep build metadata local; application errors/performance are configured separately.
|
||||
telemetry: false,
|
||||
|
||||
// For all available options, see:
|
||||
// https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/
|
||||
|
||||
// Upload a larger set of source maps for prettier stack traces (increases build time)
|
||||
widenClientFileUpload: true,
|
||||
|
||||
// PR/branch CI should validate builds without uploading source maps. Release jobs can
|
||||
// set SENTRY_UPLOAD_SOURCEMAPS=1 to enable uploads explicitly.
|
||||
sourcemaps: {
|
||||
disable: !shouldUploadSentrySourcemaps,
|
||||
},
|
||||
|
||||
// Uncomment to route browser requests to Sentry through a Next.js rewrite to circumvent ad-blockers.
|
||||
// This can increase your server load as well as your hosting bill.
|
||||
// Note: Check that the configured route will not match with your Next.js middleware, otherwise reporting of client-
|
||||
|
||||
Reference in New Issue
Block a user