mirror of
https://github.com/fluencelabs/wasm-bindgen
synced 2025-04-25 06:02:13 +00:00
32c611d16d
This commit migrates all our examples to using `wasm-pack build` to compile their code and run `wasm-bindgen`. This should make it a bit easier to understand the examples as there's less to follow during the build step. Webpack projects are all using `@wasm-tool/wasm-pack-plugin` as well so the build step is simple `npm run serve`. Other examples which retain `build.sh` are just using `wasm-pack build` now
34 lines
1.3 KiB
HTML
34 lines
1.3 KiB
HTML
<html>
|
|
<head>
|
|
<meta content="text/html;charset=utf-8" http-equiv="Content-Type"/>
|
|
</head>
|
|
<body>
|
|
<script>
|
|
// The `--no-modules`-generated JS from `wasm-bindgen` attempts to use
|
|
// `WebAssembly.instantiateStreaming` to instantiate the wasm module,
|
|
// but this doesn't work with `file://` urls. This example is frequently
|
|
// viewed by simply opening `index.html` in a browser (with a `file://`
|
|
// url), so it would fail if we were to call this function!
|
|
//
|
|
// Work around this for now by deleting the function to ensure that the
|
|
// `no_modules.js` script doesn't have access to it. You won't need this
|
|
// hack when deploying over HTTP.
|
|
delete WebAssembly.instantiateStreaming;
|
|
</script>
|
|
|
|
<!-- this is the JS generated by the `wasm-bindgen` CLI tool -->
|
|
<script src='./pkg/no_modules.js'></script>
|
|
|
|
<script>
|
|
window.addEventListener('load', async () => {
|
|
// the `wasm_bindgen` global is set to the exports of the Rust module
|
|
//
|
|
// here we tell bindgen the path to the wasm file so it can run
|
|
// initialization and return to us a promise when it's done
|
|
// also, we can use 'await' on the returned promise
|
|
await wasm_bindgen('./pkg/no_modules_bg.wasm');
|
|
});
|
|
</script>
|
|
</body>
|
|
</html>
|