* 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]>
4.7 KiB
quickjs-emscripten / quickjs-emscripten-core / QuickJSAsyncWASMModule
Class: QuickJSAsyncWASMModule
Defined in: packages/quickjs-emscripten-core/src/module-asyncify.ts:23
Asyncified version of QuickJSWASMModule.
Due to limitations of Emscripten's ASYNCIFY process, only a single async function call can happen at a time across the entire WebAssembly module.
That means that all runtimes, contexts, functions, etc created inside this WebAssembly are limited to a single concurrent async action. Multiple concurrent async actions is an error.
To allow for multiple concurrent async actions, you must create multiple WebAssembly modules.
Contents
Extends
Methods
evalCode()
evalCode():
never
Defined in: packages/quickjs-emscripten-core/src/module-asyncify.ts:76
Synchronous evalCode is not supported.
Returns
never
Overrides
evalCodeAsync()
evalCodeAsync(
code,options):Promise<unknown>
Defined in: packages/quickjs-emscripten-core/src/module-asyncify.ts:91
One-off evaluate code without needing to create a QuickJSAsyncRuntime or QuickJSAsyncContext explicitly.
This version allows for asynchronous Ecmascript module loading.
Note that only a single async action can occur at a time inside the entire WebAssembly module. Multiple concurrent async actions is an error.
See the documentation for QuickJSWASMModule#evalCode for more details.
Parameters
code
string
options
Returns
Promise<unknown>
getWasmMemory()
getWasmMemory():
Memory
Defined in: packages/quickjs-emscripten-core/src/module.ts:441
Experimental
Retrieve the WebAssembly memory used by this QuickJS module. Use this access very carefully - you are responsible for safe interaction with the memory.
To supply a custom, pre-initialized memory to QuickJS, create a new variant and provide the CustomizeVariantOptions#wasmMemory option.
Returns
Memory
Inherited from
QuickJSWASMModule.getWasmMemory
newContext()
newContext(
options?):QuickJSAsyncContext
Defined in: packages/quickjs-emscripten-core/src/module-asyncify.ts:67
A simplified API to create a new QuickJSAsyncRuntime and a QuickJSAsyncContext inside that runtime at the same time. The runtime will be disposed when the context is disposed.
Parameters
options?
ContextOptions = {}
Returns
Overrides
newRuntime()
newRuntime(
options?):QuickJSAsyncRuntime
Defined in: packages/quickjs-emscripten-core/src/module-asyncify.ts:41
Create a new async runtime inside this WebAssembly module. All runtimes inside a module are limited to a single async call at a time. For multiple concurrent async actions, create multiple WebAssembly modules.
Parameters
options?
AsyncRuntimeOptions = {}