Skip to content

v0.59.2

Choose a tag to compare

@ttraenkler ttraenkler released this 29 Jun 02:04

v0.59.2

Released 2026-06-29.

Native Messaging — all hosts re-chunk (#389)

  • #2814 — all four example hosts now re-chunk their responses to the ≤1 MiB
    browser cap
    . nm_js2wasm_deno and nm_js2wasm_wasi_p1 were echoing the whole
    message verbatim; they now stream ≤1 MiB JSON frames like
    nm_js2wasm_node_fs/nm_js2wasm_node_process, so no host sends >1 MB in a
    single message (the real Chrome native-messaging host→extension limit). Verified
    byte-exact reassembly at 1 / 64 / 128 / 256 MiB under real wasmtime v46 for all
    four. Two incidental main bugs were fixed along the way: the matrix
    node_process 64/128 MiB cases (red since #2810) and issue-2684's single-file
    compile of the bundled deno example (unsatisfiable env.runNmHost import).

Fixes

  • #2815 — suppress the spurious Cannot find name 'Deno' diagnostic for the
    recognized Deno.{stdin,stdout,stderr} surface (the multi-file analyzer wasn't
    injecting the ambient Deno d.ts the single-source path already had).
  • #2811 — capture/globalize builtin-named vars + destructuring-param closure
    TDZ-flag offset.

Docs

  • #2812 — Native Messaging deployment recipe (wasmtime shebang / bun -b /
    deno compile + manifest).
  • #2813 — running --target wasi output across runtimes (wasmtime -W flags
    • the all-proposals caveat, bun -b, deno).
  • #2817 — tracked: nm_node_process's env.__wasiStdinStop host import needs
    a WASI-native fallback.

Full changelog: v0.59.1...v0.59.2