* Migrate from Yarn to pnpm - Replace Yarn 4.0.2 with pnpm 10.29.3 as the package manager - Add pnpm-workspace.yaml and .npmrc configuration - Update all scripts to use pnpm commands - Rename getYarnWorkspaces() to getWorkspaces() in scripts/helpers.ts - Update CI workflow to use pnpm/action-setup@v4 with Node 22 - Add @jitl/tsconfig as root devDependency for proper resolution - Add variant packages as devDependencies for test resolution - Fix TypeScript 5.9 compatibility in memory.ts (Int32Array<ArrayBuffer>) - Upgrade typedoc to 0.28.17 for TypeScript 5.9 support - Upgrade typedoc-plugin-markdown to 4.10.0 - Regenerate documentation with new typedoc version * Clarify git commit --amend rule in CLAUDE.md * CI: Add --ignore-scripts to pnpm install Equivalent to yarn's YARN_ENABLE_SCRIPTS=0 - prevents prepare scripts from running during install, which would fail on a fresh checkout. * Fix pnpm tarball naming in smoketest scripts pnpm pack generates tarball names like jitl-quickjs-ffi-types-0.32.0.tgz (without @ prefix, with version) instead of @jitl-quickjs-ffi-types.tgz * Update examples to TypeScript 5.9 for compatibility The library now requires TypeScript 5.9+ due to stricter typed array generics (Int32Array<ArrayBuffer>). Update all TypeScript-using examples. * Use --legacy-peer-deps for create-react-app smoketest react-scripts@5 only supports TypeScript 3.x/4.x, but our library now requires TypeScript 5.9+ for typed array generics. Use --legacy-peer-deps to work around the peer dependency conflict. * Fix formatting issues * Fix remaining formatting issues * Add reminder to run prettier and lint before pushing * Document CI workflow in CLAUDE.md * Add typedoc.json and remark plugins for in-page table of contents - Add typedoc-plugin-remark, remark-toc, and remark-insert-headings - Configure remark plugins to generate "Contents" section for Class, Interface, Enum, TypeAlias, and Function pages - This restores the in-page TOC that lists methods/properties that was removed in typedoc-plugin-markdown 4.3.0 * Use custom remark plugin for headless TOC in docs Replace remark-insert-headings + remark-toc with a custom plugin that inserts the table of contents directly after the class description, without a separate "Contents" heading. * Revert to standard remark plugins for TOC with Contents heading Use remark-insert-headings + remark-toc instead of custom plugin. Remove mdast-util-toc dependency and custom remark-toc-headless.mjs. * Fix lockfile - remove mdast-util-toc * Ignore pnpm-lock.yaml in prettier, update .yarn to .pnpm --------- Co-authored-by: Hanzo Dev <[email protected]>
@jitl/quickjs-wasmfile-debug-sync
Variant with separate .WASM file. Supports browser ESM, NodeJS ESM, and NodeJS CommonJS.
This generated package is part of quickjs-emscripten. It contains a variant of the quickjs WASM library, and can be used with quickjs-emscripten-core.
import variant from "@jitl/quickjs-wasmfile-debug-sync"
import { newQuickJSWASMModuleFromVariant } from "quickjs-emscripten-core"
const QuickJS = await newQuickJSWASMModuleFromVariant(variant)
This variant was built with the following settings:
Library: quickjs
The original bellard/quickjs library.
Version 2025-09-13+f1139494 vendored to quickjs-emscripten on 2026-02-15.
Release mode: debug
Enables assertions and memory sanitizers. Try to run your tests against debug variants, in addition to your preferred production variant, to catch more bugs.
Exports: require import browser workerd
Exports the following in package.json for the package entrypoint:
- Exports a NodeJS-compatible CommonJS module, which is faster to load and run compared to an ESModule.
- Exports a NodeJS-compatible ESModule. Cannot be imported synchronously from a NodeJS CommonJS module.
- Exports a browser-compatible ESModule, designed to work in browsers and browser-like environments.
- Targets Cloudflare Workers.
Extra async magic? No
The default, normal build. Note that both variants support regular async functions.
Single-file, or separate .wasm file? wasm
Has a separate .wasm file. May offer better caching in your browser, and reduces the size of your JS bundle. If you have issues, try a 'singlefile' variant.
More details
Full variant JSON description:
{
"library": "quickjs",
"releaseMode": "debug",
"syncMode": "sync",
"description": "Variant with separate .WASM file. Supports browser ESM, NodeJS ESM, and NodeJS CommonJS.",
"emscriptenInclusion": "wasm",
"exports": {
"require": {
"emscriptenEnvironment": ["node"]
},
"import": {
"emscriptenEnvironment": ["node"]
},
"browser": {
"emscriptenEnvironment": ["web", "worker"]
},
"workerd": {
"emscriptenEnvironment": ["web"]
}
}
}
Variant-specific Emscripten build flags:
[
"-O0",
"-DQTS_DEBUG_MODE",
"-DDUMP_LEAKS=1",
"-gsource-map",
"-s ASSERTIONS=1",
"--pre-js $(TEMPLATES)/pre-extension.js",
"--pre-js $(TEMPLATES)/pre-sourceMapJson.js",
"--pre-js $(TEMPLATES)/pre-wasmOffsetConverter.js",
"--pre-js $(TEMPLATES)/pre-wasmMemory.js",
"-DQTS_SANITIZE_LEAK",
"-fsanitize=leak",
"-g2"
]