Not use Babel for adding debug information during build

[spaceemotion]

I wanted to try out the new Rolldown version of Vite for building our web app. Without the Sentry plugin, the whole build takes about 8 seconds.

However, with the Sentry plugin, this shoots up back to about 24 seconds again - so a 3x increase. I tried looking for why that could be the case and saw that files are being modified using Babel.

Our current Vite build takes about 30 seconds, with or without Sentry.

Here's the current configuration for the Sentry plugin that we're using:

sentryVitePlugin({
  disable: !process.env.SENTRY_RELEASE,
  telemetry: false,

  org: process.env.SENTRY_ORG,
  project: process.env.SENTRY_PROJECT,

  release: {
    dist: process.env.SENTRY_DIST,

    setCommits: {
      auto: true,
      ignoreEmpty: true,
      ignoreMissing: true,
    },
  },

  bundleSizeOptimizations: {
    excludeDebugStatements: true,
    excludeReplayShadowDom: true,
    excludeReplayIframe: true,
    excludeReplayWorker: true,
  },
}),

Are there plans to use a faster/more modern way of handling these things?

Thanks in advance!

[lforst]

As long as you don't use reactComponentAnnotations the plugin will not use babel to transform things. Ideally you profile your build somehow to figure out what exactly is slow. In general, the actual upload of the sourcemaps will probably take the longest because it is strongly I/O bound and requires quite a bit of memory.

Currently we don't have any short term plans to specifically support rolldown. At some point we will!