Repository navigation
Release wasm-split-cli 0.2.5 - #90
Merged
Merged
Conversation
matches the output of running sha256sum on the files
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.
wasm-split-cli v0.2.5
Options::cost_modelwith a bernoulli model (--cost-modelin the cli). Shared chunksare merged when that lowers the expected loading time, which weighs the requests saved against
the extra bytes loaded. This tends to cut the number of chunks one split module loads from
hundreds to tens. The default cost model depends on the target. The web target uses the
new cost model, the bundler target keeps the previous output, equivalent to
--cost-model=none.logfallback active when no subscriber is configured.