Tree shaking the bundled replay compression worker

[simhnna]

I'm failing to tree shake the compression worker away since I'm hosting my own due to CSP restrictions.

I'm using angular and I tried loading it lazily but it always ends up in the initial bundle. Is there a way to prevent that?
I'm wondering if the sdk could provide an entrypoint for the replay integration that requires specifying a worker url and doesn't include the worker itself. I guess that would be simpler than everybody trying to treeshake it away...

Here's my demo I tested with
https://github.com/simhnna/sentry-treeshaking
Here's the output of ng build

Initial chunk files   | Names         |  Raw size | Estimated transfer size
chunk-5DIU2UCZ.js     | -             | 213.31 kB |                59.12 kB
chunk-26BSX27O.js     | -             | 208.05 kB |                59.22 kB
polyfills-SCHOHYNV.js | polyfills     |  34.52 kB |                11.29 kB
main-6QWHRXFC.js      | main          |  19.32 kB |                 5.32 kB
styles-5INURTSO.css   | styles        |   0 bytes |                 0 bytes

                      | Initial total | 475.21 kB |               134.95 kB

Lazy chunk files      | Names         |  Raw size | Estimated transfer size
chunk-A5TNYZSY.js     | sentry        |   1.01 kB |                 1.01 kB
chunk-HPEDPCRC.js     | index         |  96 bytes |                96 bytes

[mydea]

Hello, this is documented here: https://docs.sentry.io/platforms/javascript/configuration/tree-shaking/

If you use a bundler that we support, you can configure bundleSizeOptimizations.excludeReplayWorker: true. Else, you can configure __SENTRY_EXCLUDE_REPLAY_WORKER__: true in your build as documented on that page to shake this code out!