@tanstack/ai-isolate-quickjs weekly downloads statistics

@tanstack/ai-isolate-quickjs

QuickJS WASM driver for TanStack AI Code Mode. Runs everywhere — Node.js, browsers, and edge runtimes — with zero native dependencies.

Installation

Usage

Config Options

• timeout — Default execution timeout in milliseconds (default: 30000) • memoryLimit — Default QuickJS runtime memory limit in MB (default: 128) • maxStackSize — Default QuickJS runtime max stack size in bytes (default: 524288) • wasmLocation — Optional URL or path from which Emscripten loads the QuickJS WASM binary. When omitted, quickjs-emscripten resolves its bundled binary.

Serving the WASM Binary

Use wasmLocation when your runtime requires the QuickJS WASM binary to be served from a public directory or CDN:

The configured file must be the synchronous release binary exported by @jitl/quickjs-wasmfile-release-sync/wasm. Ensure cross-origin requests are allowed when serving it from another origin.

Tradeoffs vs Node Driver

| | QuickJS (WASM) | Node (isolated-vm) |

| Native deps | None | Yes (C++ addon) | | Browser support | Yes | No | | Performance | Slower (interpreted) | Faster (V8 JIT) | | Memory limit | Configurable | Configurable | | Best for | Browser, edge, portability | Server-side performance |

How It Works

Uses QuickJS compiled to WebAssembly via quickjs-emscripten. Each execution creates a fresh QuickJS context with tool bindings injected as global async functions.

Runtime Limits and Errors

• QuickJS enforces runtime memory and stack limits for each context. • Exceeding limits can produce normalized errors such as MemoryLimitError or StackOverflowError. • Certain fatal limit conditions may dispose the underlying VM; create a fresh context before running more code after disposal.

License

MIT

Description from the npm listing.