2019-02-25 11:11:30 -08:00
|
|
|
<html>
|
|
|
|
|
<head>
|
|
|
|
|
<meta content="text/html;charset=utf-8" http-equiv="Content-Type"/>
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
<!-- Include the JS generated by `wasm-pack build` -->
|
|
|
|
|
<script src='pkg/without_a_bundler_no_modules.js'></script>
|
|
|
|
|
|
|
|
|
|
<script type=module>
|
2019-03-07 07:33:40 -08:00
|
|
|
// Like with the `--web` output the exports are immediately available
|
|
|
|
|
// but they won't work until we initialize the module. Unlike `--web`,
|
2019-02-25 11:11:30 -08:00
|
|
|
// however, the globals are all stored on a `wasm_bindgen` global. The
|
|
|
|
|
// global itself is the initialization function and then the properties of
|
|
|
|
|
// the global are all the exported functions.
|
|
|
|
|
//
|
|
|
|
|
// Note that the name `wasm_bindgen` can be configured with the
|
|
|
|
|
// `--no-modules-global` CLI flag
|
|
|
|
|
const { add } = wasm_bindgen;
|
|
|
|
|
|
|
|
|
|
async function run() {
|
|
|
|
|
await wasm_bindgen('./pkg/without_a_bundler_no_modules_bg.wasm');
|
|
|
|
|
|
|
|
|
|
const result = add(1, 2);
|
|
|
|
|
console.log(`1 + 2 = ${result}`);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
run();
|
|
|
|
|
</script>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
