Wasm not worked in edge

Bug report

What is the current behavior? wasm is not usable on edge

If the current behavior is a bug, please provide the steps to reproduce.

• create a wasm module and import it

  import("my_wasm_module").then(m => m.greet())
  

• open edge (not chromium kernel) it would complains about TypeError: Response expected
• open edge (chromium kernel): everything works

What is the expected behavior? the wasm would generate code like this

var req = fetch(__webpack_require__.p + "" + {"b819":"b6527e0fa9c3d95b89bc"}[wasmModuleId] + ".module.wasm");
promise = WebAssembly.instantiateStreaming(req, importObject);

According to docs, the first argument should be “A Response object or a promise that will fulfill with one”, it should be happy with Promise<Response> but actually not on edge.

And I have tried in console

fetch("/my_wasm_module.wasm")
    .then(r => WebAssembly.instantiateStreaming(r, importObject))
    .then(x => console.log(x))

and works.

Other relevant information: webpack version: “4.42.0” Node.js version: v12.16.1 Operating System: Windows 10 18362.720 Additional tools: Edge (bundled with windows, not chromium kernel)

I do know it is bug in Edge, but I think we should have workaround in webpack for a wide used browser if possible.

[henriiik]

We had this issue and finally tracked it down. The promise object was being pollyfilled and that was what was causing the problem.

We are using babel and we were manually importing regenerator-runtime/runtime and core-js/stable in our entrypoint and this was the source of the problem.

We switched to using @babel/plugin-transform-runtime and that was the solution.

[alexander-akait]

Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks!