Brian Sletten (Apr 26 2024 at 23:28): Brian Sletten (Apr 26 2024 at 23:28):Hi, all, I'm new to using jco but I ran into what seems like a regression in 1.2.0 around transpilation. I'm not sure if it is related to the other one mentioned above so I created a new thread for it. I have a working installation that successfully transpiles a very simple .wasm file generated from Rust. It is using 1.1.1. I tried a new installation today and was suddenly receiving an error. I realized that it was 1.2.0 and it appears to be expecting wasm-tools.core2.wasm to be in the jco tree. It seems to be in the componentize-js tree.
Here's the error:
jco transpile add.wasm -o out-dir
node:internal/fs/promises:638
return new FileHandle(await PromisePrototypeThen(
^
Error: ENOENT: no such file or directory, open '/Users/brian/src/jco/node_modules/@bytecodealliance/jco/obj/wasm-tools.core2.wasm' <=============
at async open (node:internal/fs/promises:638:25)
at async Module.readFile (node:internal/fs/promises:1251:14)
at async fetchCompile (file:///Users/brian/src/jco/node_modules/@bytecodealliance/jco/obj/wasm-tools.js:42:32) {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/Users/brian/src/jco/node_modules/@bytecodealliance/jco/obj/wasm-tools.core2.wasm'
}
Node.js v22.0.0
When I search for it, I see it here:
find . -name "wasm-tools.core2.wasm" -print
./componentize-js/node_modules/@bytecodealliance/jco/obj/wasm-tools.core2.wasm
When I look under my working directory:
find . -name "wasm-tools.core2.wasm" -print
./jco/obj/wasm-tools.core2.wasm
Guy Bedford (Apr 27 2024 at 00:42):@Brian Sletten thanks, that was a publish bug - I've published a 1.2.1 with the fix.
Brian Sletten (Apr 27 2024 at 03:14):Guy Bedford said:
Brian Sletten thanks, that was a publish bug - I've published a 1.2.1 with the fix.
That did it. Thanks!
Last updated: Dec 23 2024 at 13:07 UTC