Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issues
#1293, #1294, #1966
Short description and why it's useful
There's been a few issues targeted at improving the bundle size, integrating bundlesize in the CI checks should help keep track of how the bundles are changing across commits and PRs so it's easier to see how big or small they get. You can check this dummy PR in my fork that adds an extra library that makes the bundle size bigger than the set maximum.
I'm just adding the app, vendor and manifest files to the check with some sensible maximum file sizes but this can be tweaked.
Screenshots of visual changes before/after (if there are any)
PR Screen
Bundle Size Details
Screenshot of passed e2e tests (if you are using our standard setup as a backend)
TBA
Upgrade Notes and Changelog
Contribution and currently important rules acceptance