(jco componentWit) Failed to decode wit component unknown component version about jco

[DougAnderson444]

Thanks for the reply! Good to know, this was driving me crazy. Will leave this here for others in the meantime, looking forward to the 0xd release 🚀🎉

[guybedford]

Landed in #86.

[DougAnderson444]

Windows 10
jco version 0.7.0

[DougAnderson444]

Steps to reproduce:

1. clone https://github.com/bytecodealliance/cargo-component
2. cd example
3. cargo component build
4. jco wit ./target/wasm32-wasi/debug/service.wasm

(jco componentWit) ComponentError: Failed to decode wit component
unknown component version: 0xd (at offset 0x0)
    at componentWit (node_modules/@bytecodealliance/jco/cli.mjs:45393:13)
    at componentWit (node_modules/@bytecodealliance/jco/cli.mjs:47121:18)
    at async node_modules/@bytecodealliance/jco/cli.mjs:47475:9

[guybedford]

This is because the upgrade for JCO from version 0xc to version 0xd of the component model is still in progress, the new release is just about ready to go, should be up soon.

[DougAnderson444]

Linking this to bytecodealliance/wasm-tools#1027 aka "0xc is dead long live 0xd" for reference

[DougAnderson444]

Thank you! You are the guy! Can't wait to use it =)

[JanKaul]

Hey, first of all thanks for the great work. Could it be that something went wrong with building the 0.8.0 release for npm. I installed the 0.8.0 version from npm, but when I run jco --version I get 0.7.0.

[DougAnderson444]

Yeah me too, which is weird because it was supposed to be fixed here #88

[DougAnderson444]

I mean here: #89

It hasn't been merged yet, but should fix it once merged

For what it's worth, I think the v8 functionality still works even though it displays v7

[JanKaul]

Great, thanks for the info