Expected behavior

WebAssembly modules loaded in either any electron context (ex, server process or render process) are usable within Electron.

Actual behavior

WebAssembly modules fail to load/run.

How to reproduce

• This repository provides a simple test and derives from the WebAssembly.org Developer's Guide. If I remember to, I will try to add a WebAssembly call in the main.js as well, but right now I don't have a nodejs version compatible with the binary version of any of my wasm files to verify I wire things together correctly.
• This repository contains the tank demo minimally packaged for electron. The live version of the tank demo can be found here.

Details

The dependency versions currently included electron support behind flags. --expose-wasm for nodejs and --enable-webassembly for chromium. In theory, web assembly support could be enabled in electron now by respecting/exposing these flags.

However, it will be less of a moving target if this waits until electron updates to Node.js v8.0 and Chrome[ium] 57. Since WebAssembly has achieved cross-browser consensus/minimum viable product, things are converging on the 0x1 version of the binary format, and supporting it in electron with the current dependency versions would probably lead to frustration and version mismatches.

Since both Chrome 57 and Node 8 will expose WebAssembly without a flag, in theory this will just work once electron updates its dependencies, but it would still be good to confirm.

Related

#6539 First raised the question of whether WebAssembly was supported in electron and has some discussion concerning the chromium flag.
#7395 (comment) Requests the chromium flag be respected to enable WebAssembly with the current dependency.
#8993 Tracks the update to Chromium 57 (or 58)