-
-
Notifications
You must be signed in to change notification settings - Fork 343
sentry is too havy for JS bundle (adds 500Kb prod) #3826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @vovkasm, Our browsers and core JS packages rely heavily on tree shaking which is not supported our of the box in React Native. We realize that and are looking for other options to optimalize the size of the SDK. I'll close this as a duplicate of #3718, we take this serious, I just want to keep all the discussion at one place. Please feel free to comment there as well as up vote the issue, that helps us prioritizing. |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 5.22.2
react-native
version: 0.73.8Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
(
@sentry/react-native
)First of all, I want to thank the team for a wonderful product that greatly helps the entire community.
However, in recent years the product has become too heavy. Its total size in the production JS bundle is equal to the size of the entire RN, about to 500Kb. This can lead to slowdown at startup for highly optimized applications.
Steps to reproduce:
@sentry/react-native
to package.json and link it according to documentationsnpx react-native bundle --entry-file index.js --platform android --dev false --bundle-output bundle0.dat --sourcemap-output bundle0.map
npx source-map-explorer --no-border-checks bundle0.dat bundle0.map
Actual result:
In out real application it looks like this

In clean RN project (as in repro)

Expected result:
I think it would be very good if the sentry weight was no more than 150Kb. I'm worried that people will stop using the sentry because it's so heavy, but it's a very good tool.
The text was updated successfully, but these errors were encountered: