chore: migrate from yarn 1 to pnpm

[josemarluedke]

Summary

Migrates the monorepo from yarn 1 to pnpm: workspace definition, lockfile, task running, and GitHub Actions. Targets feat/static-docs-export, not main.

Important

The original motivation for this PR has evaporated — read this before merging.

This was opened because CI on #210 failed five consecutive runs at yarn install with
ECONNREFUSED, and yarn 1 fetches from registry.yarnpkg.com while pnpm fetches from
registry.npmjs.org. That reasoning fit the evidence, but it was wrong: the yarn install
has since started working again with no change to that branch, so the failure was transient
infrastructure. pnpm is not needed to fix CI.

What this PR earned on its own merits is below: pnpm's strict resolution surfaced nine real
defects that yarn's flat node_modules had been hiding — including that all 11 of
@docfy/core's jest suites were silently failing to run, and that test-app-vite was
building against the published @docfy/ember-vite rather than the local workspace package.
That is the case for merging it, and it is a genuine one. But the urgency is gone, so this
is now a judgement call rather than a fix.

The interesting part: 9 latent bugs that yarn's flat node_modules was hiding

pnpm's strict resolution surfaced nine real defects. Every one was fixed by declaring the dependency that was actually being relied on — no shamefully-hoist, no node-linker=hoisted, no .npmrc at all.

Phantom dependencies — imported but never declared, satisfied by accident from a sibling:

Package	Missing	Notes
@docfy/ember	@docfy/core	Imported in 4 source files. Added to dependencies, not devDependencies, because its published declarations/ reference those types, so consumers must resolve them.
@docfy/ember-cli	@types/unist	Declared no @types/* at all while importing from 'unist'.
@docfy/ember-vite	@types/unist, @eslint/js, eslint-plugin-jest
@docfy/ember-cli	@eslint/js
@docfy/plugin-with-prose	eslint-plugin-jest

The eslint ones were found by auditing every package's config imports against its declared deps in one pass, rather than fixing them one failure at a time. That audit now reports clean.

Workspace deps resolved from the registry. All 9 cross-workspace declarations used plain semver ("^0.11.0"). pnpm 10+ defaults link-workspace-packages to false, so those fetched from npm instead of linking locally — test-app-vite was building against the published @docfy/ember-vite@0.11.0. Converted to workspace:^0.11.0. The alternative, link-workspace-packages=true, is exactly the workaround this migration set out to avoid.

Three tsconfigs hardcoded typeRoots to the repo-root node_modules/@types, which only exists under a hoisted layout. Under pnpm this left @types/jest unresolvable and all 11 of @docfy/core's jest suites failed to run. Each now points at its own package's node_modules.

pnpm 11 specifics worth knowing

• overrides live in pnpm-workspace.yaml, not package.json. A pnpm.overrides block in the manifest is silently ignored. With it there, @types/unist resolved to 2.0.11, whose generic Node breaks @docfy/ember-cli's compile; moved to the workspace file, it correctly pins 2.0.3 — preserving what yarn's resolutions did.
• Build scripts are blocked by default. esbuild's postinstall installs its platform binary (vite cannot build without it) and nx is lerna's engine, so both are allowed via allowBuilds. core-js 2.x only prints a funding banner and stays off.

Task running

Root scripts move to pnpm's native recursive runner. compile deliberately omits --parallel so it stays topological — @docfy/core builds before @docfy/ember-vite typechecks against its lib/types. lerna is retained solely for version/publish, with npmClient: pnpm and the dead command.bootstrap block removed (lerna 9 has no bootstrap).

concurrently prefixes went yarn: → pnpm:; verified safe, since concurrently 9.2.0 parses ^(npm|yarn|pnpm|bun|node|deno).

Verification

• pnpm install --frozen-lockfile clean from a fully wiped tree
• pnpm compile green after deleting all build outputs
• @docfy/core: 11 suites, 57 tests — these were failing to run before the tsconfig fix
• @docfy/ember-vite: 60 tests
• test-app-vite builds and the base PR's static export still works — 15 .md files, llms.txt with its # Docfy H1, all 15 root-relative links resolving. This was the key regression gate.
• test-app-classic builds successfully under strict pnpm — the migration's primary risk, cleared with no hoisting workarounds
• Lint passes for core, plugin-with-prose, ember-vite

Two pre-existing failures, verified not caused by this change

1. packages/ember lint — a no-nested-splattributes template violation and a typescript-eslint config conflict (project and projectService both set). Neither is a resolution error, and CI has the lint step commented out, so they were never enforced.
2. @docfy/plugin-with-prose jest — 2 snapshot failures. The snapshots predate jest 29's snapshotFormat change (Array [ → [); the old yarn.lock resolved jest 29.7.0 too, so this failed identically before. CI only ran packages/core, so it went unnoticed.

Both are left alone as out of scope.

Needs your action

Netlify. The install phase should switch to pnpm automatically now that pnpm-lock.yaml is the only lockfile, but the build command, publish directory, and base directory for docfy-site and docfy-test-app-classic live only in the Netlify UI. If either build command names yarn, that deploy will still fail. No [build] blocks were added here rather than guess at values I cannot see.

Before publishing. The workspace: protocol must be replaced with real ranges at publish time. pnpm publish does this automatically; please confirm lerna publish does too for this setup, or published manifests would carry unresolvable workspace: specifiers.

🤖 Generated with Claude Code