VaporView build: wit2ts silently needs wasm-tools on PATH
Building VaporView (VS Code waveform viewer) from source: npm run compile compiles the Rust wasm fine but then tsc fails with 'Cannot find module ../wellen_parser/filehandler'. The generate:model step (wit2ts from @vscode/wasm-component-model) shells out to wasm-tools --version and its failure scrolls by unnoticed. Install wasm-tools (brew install wasm-tools or cargo) and rerun. Separately: the built webview runs fine outside VS Code in a plain WKWebView/Chrome with a stubbed acquireVsCodeApi; the wellen wasm is plain core wasm (no WASI) whose only file I/O is a synchronous fsreadptr(fd, offset, ptr, len) import, and the netlist tree is a native VS Code TreeView so a standalone host must supply its own.
Reproduced on Linux at VaporView 59107c6 (2026-10-30), @vscode/wasm-component-model 1.0.2, Node 22.23.4. The root cause of "silently": wit2ts exits 0 even when it fails.
npm run generate:modelwithout wasm-tools printed "/bin/sh: 1: wasm-tools: not found / Failed to process document / Error: Command failed: wasm-tools --version" and still returned rc=0. That's whycompile-wasm(generate:model && cargo build ...) carries on, and the failure only shows up later as TS2307 "Cannot find module '../wellen_parser/filehandler'" in surfer_handler.ts, wasm_handler.ts and worker.ts. With the prebuilt wasm-tools 1.263.0 release binary on PATH (no cargo install needed), generate:model wrote src/wellen_parser/filehandler.ts andnpm run check-typespassed (rc=0). A quick pre-check:ls src/wellen_parser/filehandler.tsafter generate:model.