v0.59.2
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_denoandnm_js2wasm_wasi_p1were 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_process64/128 MiB cases (red since #2810) andissue-2684's single-file
compile of the bundled deno example (unsatisfiableenv.runNmHostimport).
Fixes
- #2815 — suppress the spurious
Cannot find name 'Deno'diagnostic for the
recognizedDeno.{stdin,stdout,stderr}surface (the multi-file analyzer wasn't
injecting the ambientDenod.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 wasioutput across runtimes (wasmtime-Wflags- the all-proposals caveat,
bun -b, deno).
- the all-proposals caveat,
- #2817 — tracked:
nm_node_process'senv.__wasiStdinStophost import needs
a WASI-native fallback.
Full changelog: v0.59.1...v0.59.2