Skip to content
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

ci: Update size-limit to ensure bundle size optimization #13571

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

mydea
Copy link
Member

@mydea mydea commented Sep 3, 2024

I wanted to add a new entry for size limit with sentry browser with max. tree shaking. While doing this, I noticed that bundle size did not shrink as much as I would have expected it. After playing around some, I noticed that it was not actually shaking out the constant changes, for whatever reason. Probably some size-limit internal default config.

Now, i actually add terser to ensure it fully minimizes & tree shakes stuff for us.

@mydea mydea self-assigned this Sep 3, 2024
Copy link
Contributor

github-actions bot commented Sep 3, 2024

size-limit report 📦

⚠️ Warning: Base artifact is not the latest one, because the latest workflow run is not done yet. This may lead to incorrect results. Try to re-run all tests to get up to date results.

Path Size % Change Change
@sentry/browser 22.52 KB - -
@sentry/browser (incl. Tracing) 34.77 KB - -
@sentry/browser (incl. Tracing, Replay) 71.22 KB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 61.66 KB -4.4% -2.83 KB 🔽
@sentry/browser (incl. Tracing, Replay with Canvas) 75.56 KB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 88.29 KB - -
@sentry/browser (incl. Tracing, Replay, Feedback, metrics) 90.13 KB - -
@sentry/browser (incl. metrics) 26.83 KB - -
@sentry/browser (incl. Feedback) 39.59 KB - -
@sentry/browser (incl. sendFeedback) 27.18 KB - -
@sentry/browser (incl. FeedbackAsync) 31.9 KB - -
@sentry/react 25.28 KB -0.01% -1 B 🔽
@sentry/react (incl. Tracing) 37.74 KB +0.01% +1 B 🔺
@sentry/vue 26.67 KB - -
@sentry/vue (incl. Tracing) 36.6 KB - -
@sentry/svelte 22.65 KB - -
CDN Bundle 23.77 KB - -
CDN Bundle (incl. Tracing) 36.49 KB - -
CDN Bundle (incl. Tracing, Replay) 70.9 KB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 76.21 KB - -
CDN Bundle - uncompressed 69.61 KB - -
CDN Bundle (incl. Tracing) - uncompressed 108.2 KB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 219.84 KB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 233.04 KB - -
@sentry/nextjs (client) 37.5 KB -0.01% -3 B 🔽
@sentry/sveltekit (client) 35.35 KB - -
@sentry/node 116.43 KB +0.01% +10 B 🔺
@sentry/node - without tracing 90.18 KB +0.19% +169 B 🔺
@sentry/aws-serverless 99.47 KB +0.03% +21 B 🔺
@sentry/browser - with treeshaking flags 21.29 KB added added

View base workflow run

@mydea mydea marked this pull request as ready for review September 4, 2024 07:56
@mydea mydea merged commit ec7d9e3 into develop Sep 4, 2024
130 checks passed
@mydea mydea deleted the fn/fix-size-limit-terser branch September 4, 2024 09:08
lforst added a commit that referenced this pull request Sep 30, 2024
The peer dependency introduced in
#13571 seems to be
too strict.
After installing the latest next version (14.2.13) and @sentry/next
version (8.32.0), I get the following:
```sh
└─┬ @sentry/nextjs 8.32.0
  └── ✕ unmet peer webpack@5.94.0: found 5.95.0
```

---------

Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants