Packages

quickjs-wasi

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

Upgrading quickjs-wasi From 1.3.0 to 3.7.0

19 releases in betweenevery note read

Reading releases, release notes and advisories…

  1. 1.3.0yours
  2. 2.0.0major
  3. 2 releases
  4. 2.2.0security
  5. 3.0.0major
  6. 2 releases
  7. 3.1.0security
  8. 4 releases
  9. 3.5.0security
  10. 5 releases
  11. 3.7.0target

Before you upgrade

Tick each one off as you go
  • Breaking3.0.0
  • Breaking2.0.0

Security

  • Update quickjs-ng from v0.15.1 to v0.16.2: brings the iterator chunking/includes/join proposals, the Error.prototype.stack accessor proposal, a faster register-based regexp engine, a new arena allocator, and many correctness/security fixes.

    3.5.0
  • Resolve Dependabot security advisories by updating dev/demo dependencies and adding pnpm overrides for transitive packages pinned to vulnerable versions. Also move the repo-only pnpm configuration (overrides, onlyBuiltDependencies) out of package.json and into pnpm-workspace.yaml so it is no longer included in the published package. The published artifact has no JS dependencies, so this does not affect consumers at runtime.

    3.1.0
  • Add intrinsics option to QuickJS.create() for controlling which built-in JavaScript features are available in the VM. Pass a bitmask of Intrinsics.* flags to create a minimal sandbox — for example, omit Intrinsics.PROXY to disallow Proxy, or omit Intrinsics.DATE to remove Date. Useful for security hardening or reducing memory usage. Note: Intrinsics.EVAL must be included for vm.evalCode() to work; without it, only pre-compiled bytecode via vm.evalBytecode() can be executed.

    2.2.0

Release by release

  1. 3.7.0

    13 Nov 20262 new
    • New

      Add vm.getAllocatedSize(), a constant-time read of the bytes the runtime has allocated: the value memoryLimit is enforced against. Unlike vm.getMemoryUsage(), which walks the whole heap, its cost doesn't grow with heap size, so it suits frequent sampling. getMemoryUsage() also reports the same value as a new allocatedSize field.

    • New

      Update QuickJS-NG from v0.17.0 to v0.18.0. Out-of-memory errors (InternalError: out of memory) can no longer be caught by guest code: guest catch/finally blocks are skipped and the error propagates to the host as a JSException, leaving the VM usable. The release also includes fixes for String.prototype.repeat, Reflect.set, computed property assignment order, template literal conversion, Date.parse with Unicode spaces, and several memory leaks.

  2. 3.6.4

    6 Nov 20266 fixes
    • Fixed

      Preserve native exceptions instead of dispatching a host callback when callback-name encoding fails.

    • Fixed

      Surface native Deferred resolver failures and release both resolvers even when invocation fails, while preserving one-shot settlement.

    • Fixed

      Reject failed host-function construction without retaining callbacks, preserve earlier pending exceptions on success, and roll back incomplete Promise subscriptions.

    • Fixed

      Propagate guest allocation and property write exceptions from host data construction instead of returning exception handles or partially populated values. Release partial conversions and preserve native exceptions across host callbacks, module loaders, and handle-scope boundaries.

    • Fixed

      Throw on failed host Promise construction before publishing a Deferred, release partial resolver ownership, and preserve earlier pending exceptions on success.

    • Fixed

      Terminate the VM and reject its host Promise observers when automatic host-Promise settlement or draining fails. Preserve the original host failure, ignore late completions after disposal, and keep private resolver handles alive across scope exit. Ordinary guest rejection remains a resolved error result; synchronous failures and interruptHandler interrupts remain recoverable.

  3. 3.6.3

    19 Oct 20261 fix
    • Fixed

      Release both deferred promise resolvers after the first settlement so the unused resolver does not retain the promise and its payload until VM disposal.

  4. 3.6.2

    19 Sep 20261 fix
    • Fixed

      Update QuickJS-NG to v0.17.0, replacing the unreleased commit pin with an upstream release that includes WASI stack overflow protection.

  5. 3.6.1

    17 Sep 20262 fixes
    • Fixed

      Settle synchronous module namespace promises without draining unrelated guest jobs. Preserve deferred resolution for asynchronous modules and namespaces exporting then.

    • Fixed

      Include the wrapper's MIT license and copyright notice in the npm package.

  6. 3.6.0

    25 Aug 20261 new
    • New

      Add the maxStackSize option and MAX_STACK_SIZE ceiling so WASI stack overflow can be caught by guest JavaScript without exhausting the physical WebAssembly stack.

  7. 3.5.0

    Security fix20 Aug 20262 new · 2 fixes
    • Security

      Update quickjs-ng from v0.15.1 to v0.16.2: brings the iterator chunking/includes/join proposals, the Error.prototype.stack accessor proposal, a faster register-based regexp engine, a new arena allocator, and many correctness/security fixes.

    • New

      Add handle.className: the engine-level class name of a value (e.g. "Map", "Date", "URL") read trap-free from the class table — unlike constructorName, it executes no guest code and cannot be spoofed by prototype/constructor reassignment.

    • New

      Add vm.markPromiseHandled(promise): suppress the onUnhandledRejection callback for a promise whose rejection the host observes through other means.

    • Fixed

      resolvePromise(), Deferred.settled, and module namespace resolution now subscribe via quickjs-ng's engine-level JS_PromiseThen instead of a captured Promise.prototype.then, so guest code that patches then or Symbol.species can no longer intercept or observe host promise subscriptions.

    • Fixed

      Exceeding memoryLimit throws InternalError: out of memory again instead of a bare null (regression in 3.3.1): the limit is now enforced in the WASI malloc layer, which reserves headroom below the limit so the OOM error object can always be constructed.

  8. 3.4.0

    6 Aug 20262 new
    • New

      Strings now cross the WASM boundary losslessly in both directions — embedded NULs and lone surrogates survive toString(), newString(), evalCode() sources, property keys, and enumeration.

    • New

      Add vm.exportHandle() / vm.importHandle() for snapshot-portable handle tokens, enabling pre-snapshot captures to be re-materialized in restored VMs without executing guest code.

2 other lines we could not sort, mostly version bumps
  • Errors thrown by moduleLoader.load / moduleLoader.normalize now propagate to the guest with their real message instead of being swallowed and replaced by a generic could not load module error.

    3.1.0
  • Returning a Promise (an async callback) from load or normalize now throws a clear TypeError explaining that the callbacks must be synchronous, instead of coercing the Promise to source text and failing with a confusing SyntaxError. For async module sources (e.g. loading over https://), see the fetch-and-retry pattern documented in the README's "ES Modules" section.

    3.1.0

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.