Due to the changes in emscripten you mentioned, my own WASM example code now
compiles and runs fine with the following simple nim.cfg:
@if emscripten:
cc = clang
clang.exe = "emcc"
clang.linkerexe = "emcc"
cpu = i386
@end
Run
and this command line:
`nim c -d:emscripten -d:release -d:danger -o:<progname>.html <progname>.nim`
For ASM.js output,
-t:"-s WASM=0" -l:"-s WASM=0"
Run
is inserted into the command line. I'm running Nim 0.20 and emscripten 1.38.38
on Linux 64bit, so your problem might be specific to Windows or to your code.