-
-
Notifications
You must be signed in to change notification settings - Fork 3
chore(deps-dev): bump @size-limit/time from 13.1.1 to 14.0.0 #609
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
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot WHY are you increasing these values?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because
size-limit14 changes how these checks are measured.@size-limit/preset-small-libmoved to rolldown by default in v14, so the reported bundle sizes increased even though the library code did not. I raised only the limits that started failing sonpm run sizewould pass with the new toolchain.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot Why does rolldown cause the bundle size to be larger
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because
@size-limit/preset-small-libswitched fromesbuildin 13.1.1 torolldownin 14.0.0. Different bundlers make different tree-shaking, interop, and minification choices, so the measured bundled output can change even when this repo’s source code does not. In this PR the increase looks like toolchain drift from that bundler swap, not a library code-size regression.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot my question is not a generic why, I want an analysis of what is not being tree-shaken
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dug into the actual saved
size-limitbundles from 13.1.1 vs 14.0.0 for this repo. For the selective cases ({ getWindow }and thees5-envimport set), I do not see an unrelated module/API staying live — both versions pull the same dependency closure around the lazy global lookup/cache helpers (safe,_getGlobalValue,_getGlobalConfig, cached-value wrapper, lazy accessor). The big difference is that the 14.0.0 rolldown output is much less aggressively collapsed/minified:es5-envgoes from 1303B to 1690B,getWindowfrom 927B to 1126B, and the full bundle from 37657B to 55351B. So my current read is: this is not one obvious thing failing to tree-shake; it’s mostly a bundler/output-optimization difference in the new preset.