chore(deps): bump to beamterm 1.0.0

[junkdog]

probably (hopefully) the last bump in a while. version should be cargo update-able too, going forward.

the release is otherwise pretty uninteresting from a ratzilla pov. dropped at least one dep, so that's good.

beamterm 1.0.0 will probably be released before the next ratzilla release, so might as well hold off on merging. 0.18.0 mostly revolves around native/not-wasm stuff + final api audit.

[orhun]

Tried to run the demo but hitting this:

it looks like the Rust project used to create this Wasm file was linked against
version of wasm-bindgen that uses a different bindgen format than this binary:

  rust Wasm file schema version: 0.2.117
     this binary schema version: 0.2.106 (11831fb89)

Currently the bindgen format is unstable enough that these two schema versions
must exactly match. You can accomplish this by either updating this binary or
the wasm-bindgen dependency in the Rust project.

You should be able to update the wasm-bindgen dependency with:

    cargo update -p wasm-bindgen --precise 0.2.106 (11831fb89)

don't forget to recompile your Wasm file! Alternatively, you can update the
binary with:

    cargo install -f wasm-bindgen-cli --version 0.2.117

if this warning fails to go away though and you're not sure what to do feel free
to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues!

2026-04-03T17:31:34.615182Z ERROR ❌ error
error from build pipeline

Caused by:
    0: HTML build pipeline failed (1 errors), showing first
    1: error from asset pipeline
    2: running wasm-bindgen
    3: wasm-bindgen call to executable '/home/orhun/.cache/trunk/wasm-bindgen-0.2.106/wasm-bindgen' with args: '["--target=web", "--out-dir=/drv/cargo/target/wasm-bindgen/debug", "--out-name=demo2", "/drv/cargo/target/wasm32-unknown-unknown/debug/demo2.wasm", "--no-typescript"]' returned a bad status: exit status: 1

Probably a skill issue

[junkdog]

i think your wasm-bindgen-cli is too old; the lock file requires 0.2.108 but you have 0.2.106.

[orhun]

That's weird:

$ wasm-bindgen -V
wasm-bindgen 0.2.117

Then I realized it's using the locally downloaded binary from cache...

I deleted the cache and it still tried to install 0.2.106:

$ rm /home/orhun/.cache/trunk/

$ trunk serve
2026-04-04T18:16:11.741357Z  INFO 🚀 Starting trunk 0.21.14
2026-04-04T18:16:11.872795Z  INFO 📦 starting build
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.08s
2026-04-04T18:16:12.244289Z  INFO downloading wasm-bindgen version="0.2.106"

Then I placed Trunk.toml next to the example dir:

[tools]
wasm_bindgen = "0.2.117"

Then it used the already-installed version and it all worked fine:

$ trunk serve
2026-04-04T18:20:45.351198Z  INFO 🚀 Starting trunk 0.21.14
2026-04-04T18:20:45.352923Z  INFO 📦 starting build
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.09s
2026-04-04T18:20:46.427512Z  INFO applying new distribution
2026-04-04T18:20:46.428819Z  INFO ✅ success
2026-04-04T18:20:46.428918Z  INFO 📡 serving static assets at -> /
2026-04-04T18:20:46.429319Z  INFO 📡 server listening at:
2026-04-04T18:20:46.429338Z  INFO     🏠 http://127.0.0.1:8080/
2026-04-04T18:20:46.429490Z  INFO     🏠 http://localhost.:8080/

I'm wondering if we override the wasm_bindgen version elsewhere in the repo?

Also related: trunk-rs/trunk#935

[junkdog]

I'm wondering if we override the wasm_bindgen version elsewhere in the repo?

ok, think it was due to each of us having a different Cargo.lock under examples/ - which pulled in the wrong wasm version in your case. i've un-ignored it so it should work better now.

[orhun]

Yup, I just deleted Cargo.lock and it worked as expected 👍🏼