@sentry/node package size is pretty big

[Siilwyn]

👋 hi there, I'm using Sentry for fatal error reporting on a CLI tool and a lambda server and I'm looking into moving from raven to @sentry/node. However I noticed that the package size has increased from 170kB to 1.7MB.
I'm trying to keep the CLI size down without so the parsing time is low when started, same for the server.

@sentry/node

raven

Inspecting locally the biggest offenders are:

Seems like the double dist and esm output does not work in the size favor, thoughts?

[Siilwyn]

💭 One simple opportunity would be to have the promise implementation being passed as input so the consumer can decide if a polyfill is needed.

[denizdogan]

Using @sentry/browser in a React project and bundling with Parcel, ~102 kB of the bundle (more than 25% of the total size) comes from the Sentry dependency. If there's anything I can do to reduce the size of this dependency, let me know! 👍

[kamilogorek]

@denizdogan it's 17.7kB gzipped - https://bundlephobia.com/result?p=@sentry/browser@5.11.2 🤔

[denizdogan]

@kamilogorek That's weird, maybe it's just the way that I use Parcel that's making it this way? Because my output bundle size is 393.07 kB and using a bundle visualizer tool, it looks like @sentry/browser takes 38 kB. Then a bunch of other Sentry libraries (assuming they're dependencies) take up the rest of the 102 kB.

[kamilogorek]

@denizdogan can you explain how you visialize this exactly? I can take a look at it if you provide a small repro case

[denizdogan]

@kamilogorek I've made a small reproduction repository with instructions here: https://github.com/denizdogan/sentry-parcel-bundle-size Thanks!

[kamilogorek]

@denizdogan not sure what's the state of Parcel 1, but I checked and it indeed produces much bigger bundle than let's say Webpack.

However, parcel@next, which is alpha version of v2, works great with basic config:

/sentry/repros/sentry-parcel-bundle-size:(master) λ: ls -alh dist/browser/
-rw-r--r--  1 kamilogorek  staff    58K Jan 30 15:19 index.js
/sentry/repros/sentry-parcel-bundle-size:(master) λ: gzip -9 dist/browser/index.js
/sentry/repros/sentry-parcel-bundle-size:(master) λ: ls -alh dist/browser/
-rw-r--r--  1 kamilogorek  staff    17K Jan 30 15:19 index.js.gz

Add this parcel config to package.json:

  "targets": {
    "browser": {
      "context": "browser",
      "includeNodeModules": true,
      "outputFormat": "global"
    }
  }

npm i parcel@next and then npx parcel@next bundle src/index.js

[denizdogan]

@kamilogorek I'll just attribute the problem to Parcel 1 then :) Thanks for your help

[chaffeqa]

been lookin into why this hasnt been brought up... so according to webpack bundle visualizer, even after all terser optimizations, the browser version is still one of the biggest deps in our bundle:

Is there any work being done to reduce this? i just find it hard to believe that the error reporting bundle is nearly as big as react (the core of the app)

[jontelm]

I see the same with the browser bundle

[ricardovanlaarhoven]

My sentry is 65KB parsed and gzipped 18kb which is the same as the whole Vue package, and even larger then Vuetify!
Even if it's 18kb gzipped this is about 20% of my application's chunk-venoders/start up javascript

[STEVEOO6]

@ricardovanlaarhoven ditto!

[timuric]

The size is enormous for an error tracking utility

[peterbakonyi05]

I can also confirm this as a big issue, probably the only reason why we are still considering to use other error reporting tools since performance is really important in most apps.

In our vendor bundle Sentry is the third biggest dependency:

• material ui components: 51kB
• react dom production: 35kB
• sentry: 21kB

[kamilogorek]

@peterbakonyi05 we already working on it, fingers crossed for a fast delivery :)