mirror of
https://github.com/fluencelabs/wasm-bindgen
synced 2025-03-30 08:51:05 +00:00
cd3781cb73
This commit reverts part of the implementation of [RFC 6]. That RFC specified that the `--browser` flag was going to be repurposed for the new "natively loadable as ES module output", but unfortunately the breakage is far broader than initially expected. It turns out that `wasm-pack` passes `--browser` by default which means that a change to break `--browser` would break all historical versions of `wasm-pack` which is a bit much for now. To solve this the `--browser` flag is going back to what it represents on the current released version of `wasm-bindgen` (optimize away some node.js checks in a few places for bundler-style output) and a new `--web` flag is being introduced as the new deployment strategy. [RFC 6]: https://github.com/rustwasm/rfcs/pull/6 Closes #1318
Without a Bundler Using --no-modules
View documentation for this example online
You can build the example locally with:
$ wasm-pack build --target no-modules
and then opening index.html in a browser should run the example!
Note that this example is in contrast to the without a bundler example
which performs a similar purpose except it uses --no-modules instead of
--web. The main difference here is how the shim JS and module are loaded,
where this example uses old-school script tags while --web uses ES
modules.