I get the same warning in Firefox when using node.js's http-server (I never noticed this before though, I guess it's a new Firefox feature), but the response content-type looks alright IMHO (application/wasm; charset=utf-8).
Interestingly, I used to get this JS warning in Chrome when using the python SimpleHttpServer module for serving, and this definitely did not set the right content-type for wasm files. Switching to node's http-server fixed this message in Chrome. I guess it's a Firefox bug *shrugs*. This is how I run http-server: http-server -c-1 -g -o "-o" opens the browser after starting "-g" serves files compressed "-c-1" disabled caching Cheers! On Wednesday, 8 January 2020 02:22:46 UTC+1, キャロウ マーク wrote: > > When I run my JS app (in Firefox 71.0) that calls an Emscripten compiled > module that uses embind to communicate with c++ code, I get the following > error in the browser’s Web Console 2 times. > > wasm streaming compile failed: TypeError: Response has unsupported > MIME type > > I am using the node.js http server module which I have just updated. Is > there some mime-type setting I need to change to make streaming compile > work? If so, how? > > Regards > > -Mark > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/36329977-7609-460a-a393-9655c294e517%40googlegroups.com.
