Wasmtime and jco componentize have different wasmtime config.toml requirements

[thomas9911]

Running wasmtime 33.0.0 and jco 1.11.2.

jco requires to have the cache enabled option set:

[cache]
enabled = true

wasmtime gives an error:

Caused by:
    TOML parse error at line 5, column 1
      |
    5 | enabled = true
      | ^^^^^^^
    unknown field `enabled`, expected `cache`

removing this field errors jco:

Caused by:
    TOML parse error at line 5, column 1
      |
    5 | [cache]
      | ^^^^^^^
    missing field `enabled`
    
(jco componentize) Error: Failed to initialize the compiled Wasm binary with Wizer:
Wizering failed to complete

commands ran:

jco componentize -d all -w wit -o dist/simple-result-js.wasm src/index.js

wasmtime run --invoke 'add(0,0)' dist/simple-result-js.wasm

[vados-cosmonic]

Hey @thomas9911 thanks for reporting this -- I think this is a bug at the lower level (wizer via compnentize-js) -- that said I'm happy to track it here. My best guess is that different versions of wasmtime deps may be pulling in and building configuration structures which have changed.

Would you mind sharing where you're placing that config? It's a bit unclear how lower level tools are picking up your wasmtime options at jco componentize call time.

[thomas9911]

sure it is in: ~/.config/wasmtime/config.toml