Bundlesize continues to creep up with every release

[jdelStrother]

I know you track this in your own releases, but thought it might be interesting to see the change in our app bundlesize each time Sentry gets bumped. From our CI, here's a report on how each sentry version impacted our overall bundlesize, going back to v7.57 (around June 2023):

Version bump	minified size change	minified+gzip size change
Updates @sentry/browser from 7.98.0 to 7.100.1	+349	+144
Updates @sentry/browser from 7.94.1 to 7.98.0	+111	-151
Updates @sentry/browser from 7.93.0 to 7.94.1	+1059	+330
Updates @sentry/browser from 7.92.0 to 7.93.0	+2444	+751
Updates @sentry/browser from 7.91.0 to 7.92.0	+485	+150
Updates @sentry/browser from 7.88.0 to 7.91.0	+1333	+480
Updates @sentry/browser from 7.86.0 to 7.88.0	+766	+320
Updates @sentry/browser from 7.84.0 to 7.86.0	+117	+43
Updates @sentry/browser from 7.81.1 to 7.84.0	+5359	+1425
Updates @sentry/browser from 7.80.1 to 7.81.1	+42	+11
Updates @sentry/browser from 7.80.0 to 7.80.1	+0	+0
Updates @sentry/browser from 7.77.0 to 7.80.0	+20	+10
Updates @sentry/browser from 7.76.0 to 7.77.0	+105	+34
Updates @sentry/browser from 7.74.1 to 7.76.0	+151	+45
Updates @sentry/browser from 7.74.0 to 7.74.1	+0	-3
Updates @sentry/browser from 7.73.0 to 7.74.0	+20	+4
Updates @sentry/browser from 7.72.0 to 7.73.0	-186	-53
Updates @sentry/browser from 7.71.0 to 7.72.0	+0	+0
Updates @sentry/browser from 7.70.0 to 7.71.0	-95	-16
Updates @sentry/browser from 7.69.0 to 7.70.0	+425	+126
Updates @sentry/browser from 7.68.0 to 7.69.0	+262	+107
Updates @sentry/browser from 7.66.0 to 7.68.0	+61	+39
Updates @sentry/browser from 7.65.0 to 7.66.0	+20	+10
Updates @sentry/browser from 7.64.0 to 7.65.0	+0	+0
Updates @sentry/browser from 7.63.0 to 7.64.0	+0	+0
Updates @sentry/browser from 7.61.1 to 7.63.0	+61	+37
Updates @sentry/browser from 7.60.1 to 7.61.1	-779	-194
Updates @sentry/browser from 7.60.0 to 7.60.1	+0	+0
Updates @sentry/browser from 7.58.1 to 7.60.0	+114	+35
Updates @sentry/browser from 7.57.0 to 7.58.1	+1813	+590
Total	+14057	+4274

Which isn't huge, but given we don't use any of the new features that have been added over the last 7 months, does feel a little like 14kb of dead weight. (Obviously a simplification - I'm sure there's a bunch of bug fixes/improvements in there too)

We're using @sentry/browser & @sentry/react in Webpack with tree shaking, with these imports:

import { showReportDialog, withErrorBoundary } from "@sentry/react";
import { init, Breadcrumbs, addBreadcrumb, captureMessage } from "@sentry/browser";
import { RewriteFrames } from "@sentry/integrations";

---

I'm not expecting an immediate fix or anything here - just thought it might be a useful datapoint to see the diffs on a realworld app.
It'll be interesting to see how v8 affects this. v7.0 launched with a pretty good bundle size drop, IIRC, but just about every single release since then seems to keep pushing Sentry's not-inconsiderable bundle size up and up.

[AbhiPrasad]

Hey @jdelStrother - this is because of us deprecated a lot of code that will be removed in v8. For example hub.js will go away entirely once we remove the Hub as part of v8. In addition we are dropping browser support to be minimum ES6, which will save some size. We'd rather take the bundle size increase for now to ensure the smoothest transition process for you to upgrade.

If you look at #9508 most of the tasks are around removals/dropping support - this should led to some pretty nice bundle wins!

[jdelStrother]

Yep, looking forward to v8 🙂

[AbhiPrasad]

From our CI, here's a report on how each sentry version impacted our overall bundlesize

What tool do you use to do this? If Sentry via codecov offered this (see codecov/engineering-team#655), would you use it?

Asking because separately because I'm actively helping build this out to launch in the next couple of months, would appreciate any thoughts!!

[jdelStrother]

It's a hacky homebrew solution - each of our PRs gets an automatic comment like this if it affects bundlesize -

And we use dependabot, so I ended up scraping the Github API for any dependabot PRs that upgraded Sentry to generate the table in my first comment.

We might be interested in a more full featured third-party version - ours does make it difficult to see changes over time, if you're not just interested in a single PR. Coming up with a single number that represents "bundlesize" is really hard though given multiple entrypoints / chunk splitting / lazy loading, so we have a bunch of custom hacks to try & target our specific cases better ... I'd be curious to see how third-party generic version would get around that.