Migrate from Yarn to pnpm (#246)

* 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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Clarify git commit --amend rule in CLAUDE.md

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* 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.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* 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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* 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.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* 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.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Fix formatting issues

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Fix remaining formatting issues

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Add reminder to run prettier and lint before pushing

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Document CI workflow in CLAUDE.md

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* 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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* 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.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* 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.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Fix lockfile - remove mdast-util-toc

* Ignore pnpm-lock.yaml in prettier, update .yarn to .pnpm

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

Author: justjake

.github/workflows/main.yml

@@ -29,27 +29,23 @@ jobs:
         uses: docker-practice/actions-setup-docker@1.0.8
         if: matrix.platform == 'macos-latest'
 
-      - name: Setup Node.js environment
-        uses: actions/setup-node@v3
-        with:
-          node-version: 18
-
       # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
       - uses: actions/checkout@v4
         with:
           # We need `git log` to find git-subtree versions
           fetch-depth: 0
 
-      - name: Yarn cache
-        uses: actions/cache@v3
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+
+      - name: Setup Node.js environment
+        uses: actions/setup-node@v4
         with:
-          path: "**/.yarn/cache"
-          key: ${{ hashFiles('**/yarn.lock') }}
+          node-version: 22
+          cache: 'pnpm'
 
       - name: Install dependencies
-        run: yarn install --immutable
-        env:
-          YARN_ENABLE_SCRIPTS: 0
+        run: pnpm install --frozen-lockfile --ignore-scripts
 
       - name: EMSDK cache
         uses: actions/cache@v3
@@ -60,26 +56,26 @@ jobs:
       - name: Environment info
         run: |
           echo $(which node) v$(node --version)
-          echo $(which yarn) v$(yarn --version)
+          echo $(which pnpm) v$(pnpm --version)
           echo $(which npx) v$(npx --version)
           echo $(npx which tsc) $(npx tsc --version)
           echo $(npx which tsup) $(npx tsup --version)
           echo $(npx which esbuild) v$(npx esbuild --version)
 
       - name: Build
-        run: yarn build
+        run: pnpm run build
 
       - name: Check types
-        run: yarn check:types
+        run: pnpm run check:types
 
       - name: Check package.jsons
-        run: yarn check:packages
+        run: pnpm run check:packages
 
       - name: Test
-        run: yarn test:slow
+        run: pnpm run test:slow
 
       - name: Build tarballs
-        run: yarn tarball && du -h build/tar/*
+        run: pnpm run tarball && du -h build/tar/*
 
       - name: Test release with NodeJS minimal ESModule example
         run: ./scripts/smoketest-node-minimal.ts
@@ -94,7 +90,7 @@ jobs:
         run: ./scripts/smoketest-vite.ts
 
       - name: Check lint
-        run: yarn lint
+        run: pnpm run lint
 
       - name: Check format
-        run: yarn check:format
+        run: pnpm run check:format

.npmrc

@@ -0,0 +1,8 @@
+# Use hoisted node-modules linker (like yarn's nodeLinker: node-modules)
+node-linker=hoisted
+
+# Hoist all packages to root node_modules for compatibility with yarn-style resolution
+shamefully-hoist=true
+
+# Equivalent to yarn's enableGlobalCache: false
+# pnpm uses content-addressable store by default, no need to disable

.prettierignore

@@ -1,6 +1,6 @@
 ts/generated
 quickjs
-.yarn
+.pnpm
 .*
 doc
 json-generator-dot-com-1024-rows.json
@@ -13,4 +13,5 @@ emsdk-cache
 packages/internal-tsconfig/*.d.*ts
 packages/internal-tsconfig/*.*js
 vendor
-CLAUDE.md
+CLAUDE.md
+pnpm-lock.yaml

.vscode/settings.json

@@ -11,7 +11,5 @@
     "emscripten.h": "c",
     "quickjs-atom.h": "c"
   },
-  "files.exclude": {
-    ".yarn/releases/*": true
-  }
+  "files.exclude": {}
 }

.yarn/releases/yarn-4.0.2.cjs

@@ -3,7 +3,6 @@
 ## v0.32.0
 
 - [#227](https://github.com/justjake/quickjs-emscripten/pull/227)
-
   - Re-works function binding in `newFunction` to use a different proxying strategy based on a new abstraction, `HostRef`. HostRef allows tracking references of host values from guest handles. Once all references to the HostRef object are disposed (either in the host, or GC'd in the guest), the host value will be dereferenced and become garbage collectable.
   - Functions passed to `newFunction` are interned in the runtime's `HostRefMap` until dereferenced.
   - `HostRef` is also exposed directly for use from `QuickJSContext`, see `newHostRef`, `toHostRef`, `unwrapHostRef` in the docs.
@@ -140,7 +139,6 @@ In edge cases, you might want to use the IIFE build which provides QuickJS as th
 - We now differentiate between runtime environments at build time using Node.JS package.json [export conditions in subpath exports][conditions], instead of including support for all environments in a single build. While this resolves open issues with relatively modern bundlers like webpack@5 and vite, it may cause regressions if you use an older bundler that doesn't understand the "browser" condition.
 - The release variants - RELEASE_SYNC (the default), and RELEASE_ASYNC - no longer embed the WebAssembly code inside a JS file. Instead, they attempt to load the WebAssembly code from a separate file. Very old bundlers may not understand this syntax, or your web server may not serve the .wasm files correctly. Please test in a staging environment to verify your production build works as expected.
 - quickjs-emscripten now uses [subpath exports in package.json][conditions]. Imports of specific files must be removed. The only valid import paths for quickjs-emscripten are:
-
   - `import * from 'quickjs-emscripten'` (the library)
   - `import packageJson from 'quickjs-emscripten/package.json'`
   - `import { DEBUG_SYNC, DEBUG_ASYNC, RELEASE_SYNC, RELEASE_ASYNC } from 'quickjs-emscripten/variants'` (these are exported from the main import, but are also available as their own files)
@@ -154,14 +152,12 @@ In edge cases, you might want to use the IIFE build which provides QuickJS as th
 ## v0.24.0
 
 - [#127](https://github.com/justjake/quickjs-emscripten/pull/127) Upgrade to quickjs 2023-12-09:
-
   - added Object.hasOwn, {String|Array|TypedArray}.prototype.at, {Array|TypedArray}.prototype.findLast{Index}
   - BigInt support is enabled even if CONFIG_BIGNUM disabled
   - updated to Unicode 15.0.0
   - misc bug fixes
 
 - [#125](https://github.com/justjake/quickjs-emscripten/pull/125) (thanks to @tbrockman):
-
   - Synchronizes quickjs to include the recent commit to address CVE-2023-31922.
 
 - [#111](https://github.com/justjake/quickjs-emscripten/pull/111) (thanks to @yourWaifu) ArrayBuffer and binary json encoding:
@@ -182,7 +178,6 @@ In edge cases, you might want to use the IIFE build which provides QuickJS as th
 - [#104](https://github.com/justjake/quickjs-emscripten/pull/104) BigInt support.
 - [#100](https://github.com/justjake/quickjs-emscripten/pull/100) **Breaking change** upgrade Emscripten version and switch to `async import(...)` for loading variants.
   We also drop support for older browsers and Node versions:
-
   - Node >= 16 is required
   - Safari >= 14.1 is required
   - Typescript >= 4.7 is recommended, but not required.

.yarnrc.yml

@@ -2,11 +2,11 @@
 
 ## Package Manager
 
-Use `corepack yarn` to run yarn commands, e.g.:
+Use `corepack pnpm` to run pnpm commands, e.g.:
 
-- `corepack yarn install`
-- `corepack yarn build`
-- `corepack yarn build:ts`
+- `corepack pnpm install`
+- `corepack pnpm build`
+- `corepack pnpm build:ts`
 
 ## Building Variants
 
@@ -17,7 +17,7 @@ To build a variant:
 ```bash
 cd packages/variant-quickjs-<name>
 make           # builds the C code with emscripten
-corepack yarn build:ts  # builds the TypeScript wrapper
+corepack pnpm build:ts  # builds the TypeScript wrapper
 ```
 
 ## Emscripten
@@ -31,7 +31,7 @@ corepack yarn build:ts  # builds the TypeScript wrapper
 Run all tests:
 
 ```bash
-corepack yarn test
+corepack pnpm test
 ```
 
 Run tests for a specific variant (e.g., quickjs-ng only):
@@ -49,7 +49,31 @@ Other test filters:
 
 ## Git
 
-- Never use `git commit --amend` - always create new commits
+- Never use `git commit --amend` - always create new commits. It's better to have a history of what was actually done since branches get rebased/squashed anyway when merged.
+- Before pushing, run `pnpm run prettier` and `pnpm run lint` to fix formatting and lint issues. No need to check after every commit - just before pushing.
+
+## CI Workflow
+
+After pushing a PR, monitor CI using the `gh` CLI:
+
+```bash
+# Check CI status for a PR
+gh pr checks <PR_NUMBER>
+
+# View a specific job's progress
+gh run view --job=<JOB_ID>
+
+# Get logs for failed steps
+gh run view <RUN_ID> --log-failed
+```
+
+When CI fails:
+1. Get the failed logs with `gh run view <RUN_ID> --log-failed | tail -100`
+2. Fix the issue locally
+3. Commit the fix (new commit, don't amend)
+4. Push and repeat until CI passes
+
+The full CI build takes ~20 minutes due to emscripten compilation.
 
 ## Key Files
 

CHANGELOG.md

@@ -844,19 +844,16 @@ audited. Please use with care in production settings.
 thinking comes next. Last updated 2022-03-18.
 
 1. Further work on module loading APIs:
-
    - Create modules via Javascript, instead of source text.
    - Scan source text for imports, for ahead of time or concurrent loading.
      (This is possible with third-party tools, so lower priority.)
 
 2. Higher-level tools for reading QuickJS values:
-
    - Type guard functions: `context.isArray(handle)`, `context.isPromise(handle)`, etc.
    - Iteration utilities: `context.getIterable(handle)`, `context.iterateObjectEntries(handle)`.
      This better supports user-level code to deserialize complex handle objects.
 
 3. Higher-level tools for creating QuickJS values:
-
    - Devise a way to avoid needing to mess around with handles when setting up
      the environment.
    - Consider integrating