[sentry/nextjs] sentry/tracing adds 30kb, can we opt-out ?

Problem Statement

Following the sentry/nextjs recommended approach, it’s difficult to opt-out from tracing in the browser.

The sentry/tracing adds more or less 30kb to the browser final bundle which is a hard blocker in some circumstances.

Here’s a tree map taken with the recommended approach and tested with @sentry/nextjs 6.18.2

Solution Brainstorm

I was able to remove the sentry/tracing from the browser, by importing sentry/react rather than sentry/nextjs

// import { init as sentryInit } from '@sentry/nextjs';
import { init as sentryInit } from '@sentry/react';

sentryInit({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
  // tracesSampleRate: 1.0,
});

That reduced the bundle from 103kb to 73kb

The setup is https://github.com/belgattitude/nextjs-monorepo-example/pull/1409

Is there any drawbacks or risks to this approach (apart from not sending traces) ?

[belgattitude]

@AbhiPrasad congrats it works perfect 💯 Thanks a lot

PS: Note for others, simply add this in next.config.js

  webpack: (config, { webpack }) => {
    // https://docs.sentry.io/platforms/javascript/configuration/tree-shaking
    config.plugins.push(
      new webpack.DefinePlugin({
        __SENTRY_DEBUG__: false,
        __SENTRY_TRACING__: false,
      })
    );

[AbhiPrasad]

Closing this for now since we’ve released v7: https://github.com/getsentry/sentry-javascript/releases/tag/7.0.0