Packages

quickjs-wasi

3.7.0 · 13 Nov 2026MIT14.3M / weekRepositoryHomepagenpmAtom feed

Your version

1.0.0

major9 Mar 2026Where it was published

1.3.0 is the newest release of 1.x.

In short

1 breaking2 new1 fixed

  • Breaking

    evalCode() and callFunction() now throw a JSException directly when the evaluated code or called function throws, matching standard JavaScript semantics. The unwrapResult() method and isException property have been removed — exceptions propagate naturally via try/catch.

Release note

Major Changes

  • Breaking

    evalCode() and callFunction() now throw a JSException directly when the evaluated code or called function throws, matching standard JavaScript semantics. The unwrapResult() method and isException property have been removed — exceptions propagate naturally via try/catch.

Minor Changes

  • Add JSException class that extends Error and is thrown by unwrapResult(). It exposes a handle property — a live JSValueHandle to the QuickJS exception value — allowing direct inspection of custom properties on the thrown error. Also fixes a bug where errors thrown from host callbacks were returned as regular values instead of being propagated as QuickJS exceptions.

  • Add native WASM extension support via dynamic linking. Extensions are C-based WASM shared libraries that link directly against the QuickJS C API with zero marshalling overhead. Extensions are fully compatible with snapshot/restore. Includes a proof-of-concept URL and URLSearchParams extension.

Patch Changes

  • Increase WASM stack size to 1MB to prevent stack overflow traps. The default wasi-sdk stack (~173KB) was too small for QuickJS, causing hard WASM traps instead of catchable JS exceptions during recursive operations like JSON.stringify or devalue serialization at moderate depths.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.