Hi Alon, After making wasm the default I get:
ERROR:root:FETCH not yet compatible with wasm (shared.make_fetch_worker is asm.js-specific) when I build. Can you give us an update on the fetch api? Are you working on wasm compatibility? If so, when might it be available? Workarounds? Thanks for your help! --Scott On Wednesday, May 9, 2018 at 7:51:07 PM UTC-7, Alon Zakai wrote: > > #6419 just landed on incoming (not in a tagged version yet), which > switches the default output to wasm. > > Only the default is changed - we of course still support asm.js, and will > for a very long time. But changing the default makes sense as the > recommended output for most use cases should be WebAssembly, given it has > shipped in all major browsers and platforms and is more efficient than > asm.js. > > Build with `-s WASM=0` to disable wasm and use asm.js if you want that (or > use `-s LEGACY_VM_SUPPORT=1`, which emits output that can run in older > browsers, which includes a bunch of polyfills as well as disables wasm). > > If you're already using wasm, you can remove the `-s WASM=1` you had, but > it's also ok to leave it. > > - Alon > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
