enhance(build): show bundle size diff on PRs #11757
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
dependencies
Bundle StatsHey there, this message comes from a github action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
View detailed bundle breakdownAdded
Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged No assets were unchanged |
LeoMcA
force-pushed
the
bundlesize-compare
branch
from
22c6a74 to
4ed8b5e
Compare
|
This pull request has merge conflicts that must be resolved before it can be merged. |
github-actions
bot
added
the
merge conflicts 🚧
also updates the `yarn analyze` command
LeoMcA
force-pushed
the
bundlesize-compare
branch
from
e93f6d1 to
6312cbc
Compare
github-actions
bot
removed
the
merge conflicts 🚧
This was referenced Sep 9, 2024
github-actions
bot
added
the
merge conflicts 🚧
|
This pull request has merge conflicts that must be resolved before it can be merged. |
although "deterministic" isn't when changing loaders, it *is* when changing import order - which is more important. we'll probably avoid the prior problem with changing loader config changing chunk names (but not their contents) if/when we move to named chunks
github-actions
bot
removed
the
merge conflicts 🚧
caugner
approved these changes
Sep 17, 2024
Co-authored-by: Claas Augner <[email protected]>
caugner
approved these changes
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
https://mozilla-hub.atlassian.net/browse/MP-1513
Problem
yarn analyzecommand is difficult to parseSolution
yarn analyzecommand with https://github.com/webpack-contrib/webpack-bundle-analyzerHow did you test this change?