Conditional sentry build/upload

[gmourasilva]

Hi

We have been using Sentry with Vercel and I'm looking for ways to speed things up.

Overall, we would like Sentry to run only in main. We have something like this right now:

const nextConfig = {
// our config
};

// Injected content via Sentry wizard below
const { withSentryConfig } = require('@sentry/nextjs');

// In development mode we don't use the Sentry configuration
// This allows us to use turbo mode locally
module.exports =
  process.env.NODE_ENV === 'production' &&
  process.env.VERCEL_GIT_COMMIT_REF === 'main'
    ? withSentryConfig(nextConfig, {
        // Only print logs for uploading source maps in CI
        silent: true,
        telemetry: false,
        widenClientFileUpload: true,
        hideSourceMaps: true,
        disableLogger: true,
        automaticVercelMonitors: true,
      })
    : nextConfig;

This conditional setup creates this kind of warning - no big deal

  ▲ Next.js 14.2.3
   Creating an optimized production build ...
 ⚠ Compiled with warnings
./node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/instrumentation.js
Critical dependency: the request of a dependency is an expression
Import trace for requested module:
./node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/instrumentation.js
./node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/index.js
./node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@opentelemetry/instrumentation/build/esm/platform/index.js
./node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@opentelemetry/instrumentation/build/esm/index.js
./node_modules/.pnpm/@[email protected]_@[email protected]_@[email protected]_@opentelemetr_pl2qeqninxaqmdjpg2uv2hkmfa/node_modules/@sentry/opentelemetry/cjs/index.js
./node_modules/.pnpm/@[email protected]/node_modules/@sentry/node/cjs/index.js
./node_modules/.pnpm/@[email protected]_@[email protected]_@[email protected]_@opentelemetry+api@1_spjyasaqaiax3pd74bfpdbtyjm/node_modules/@sentry/nextjs/cjs/index.server.js
./app/global-error.tsx

What I am looking for here is an alternative that

1. Avoid the warnings above (Not much of a problem)
2. Keep the build time low (this is important)
3. Work with pnpm dev --turbo with warnings (I think warning here are not a problem TBH)

I thought in always export the nextConfig with sentry:

const nextConfig = {
// our config
};

// Injected content via Sentry wizard below
const { withSentryConfig } = require('@sentry/nextjs');
const uploadToSentry =
  process.env.NODE_ENV === 'production' &&
  process.env.VERCEL_GIT_COMMIT_REF === 'main';

module.exports = withSentryConfig(nextConfig, {
  silent: true,
  telemetry: false,
  widenClientFileUpload: uploadToSentry, // ← here is the change
  hideSourceMaps: true,
  disableLogger: true,
  automaticVercelMonitors: true,
});

What is the best option to keep builds time low if I want to opt out Sentry?