chore(wasm): use release-wasi profile#11131
Merged
Conversation
✅ Deploy Preview for rspack canceled.
|
Contributor
📦 Binary Size-limit
🙈 Size remains the same at 48.97MB |
CodSpeed Performance ReportMerging #11131 will not alter performanceComparing Summary
|
stormslowly
approved these changes
Jul 23, 2025
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
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
release-wasi profile set
opt-level = "s", which produce smaller wasm file. See https://github.com/web-infra-dev/rspack/actions/runs/16461149283. I separate the jobs withifcondition because I will postproccess wasm file withwasm-optin next pr.BTW, I also remove "unset"s because we don't use jemallocator any more.
Related links
Checklist