Switch the --browser argument to --web
#1328
Merged
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.
This commit reverts part of the implementation of RFC 6. That RFC
specified that the
--browserflag was going to be repurposed for thenew "natively loadable as ES module output", but unfortunately the
breakage is far broader than initially expected. It turns out that
wasm-packpasses--browserby default which means that a change tobreak
--browserwould break all historical versions ofwasm-packwhich is a bit much for now.
To solve this the
--browserflag is going back to what it representson the current released version of
wasm-bindgen(optimize away somenode.js checks in a few places for bundler-style output) and a new
--webflag is being introduced as the new deployment strategy.Closes #1318