If you run the engine Basis example on GitHub and open Chrome Dev Tools, you don’t get that error. If you look at the Network tab, you’ll see that basis.wasm.wasm is served with a Response Header with Content-Type: application/wasm.
I believe this is why stream compilation of the WASM module fails. So it’s really a server configuration issue. If you set up .wasm with an application/wasm mime type in your server configuration, I suspect this will be solved.
Thanks @will, very true, I also found this out. But I must come up with a solution for my probject as it need to compile for production. This is been done using Webpack. The whole today I was figuring out whats going on and soon will come up with a solution. In my case it will be a Webpack config change for Vue.js. Also if someone is interested I found this very useful:
I should probably mention that stream compilation of WASM is really just an optimization (where compilation can start before download completes). Even if it fails, it should just fall back to compiling after download of the WASM module is fully complete.