And because of the above discussion (even though n...

# javascript

[loke]

And because of the above discussion (even though no one has suggested JS is being dropped, it just appears to have lower priority), I have no started to port my application to wasm, starting with one of the more self-contained subprojects. Once I did the manual work, changing all the js() invocations, I tried to run the tests. That gives me the following error which gives me absolutely nothing when I search for it.

Does anyone have any idea what's going on?

> Task :mpbignum:wasmJsNodeTest FAILED
file:///home/elias/prog/array/build/js/packages/array-mpbignum-wasm-js-test/kotlin/array-mpbignum-wasm-js-test.uninstantiated.mjs:218
        const wasmModule = new WebAssembly.Module(wasmBuffer);
                           ^
CompileError: WebAssembly.Module(): invalid value type 0x71 @+348
    at instantiate (file:///home/elias/prog/array/build/js/packages/array-mpbignum-wasm-js-test/kotlin/array-mpbignum-wasm-js-test.uninstantiated.mjs:218:28)
    at async file:///home/elias/prog/array/build/js/packages/array-mpbignum-wasm-js-test/kotlin/array-mpbignum-wasm-js-test.mjs:3:17
Node.js v18.12.1
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':mpbignum:wasmJsNodeTest'.
> command '/home/elias/.gradle/nodejs/node-v18.12.1-linux-x64/bin/node' exited with errors (exit code: 1)

[jw]

You should ask in #webassembly

Until https://github.com/nodejs/node/pull/50115 lands, you can specify a dev version of Node with https://youtrack.jetbrains.com/issue/KT-63014/Running-tests-with-wasmJs-in-1.9.20-requires-Chrome-Canary#focus=Comments-27-8321383.0-0

[Edoardo Luppi]

See https://github.com/lppedd/antlr-kotlin/blob/53e33f02980980141d841b64797f37cbaf215ede/antlr-kotlin-runtime/build.gradle.kts#L79-L97