You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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
Beta Was this translation helpful? Give feedback.
All reactions