Marcos Paulo
48c31dc1b3
Ten git worktrees each carried their own 225 MB node_modules (1.1 GB across five) and paid 11s per `npm ci`. pnpm hardlinks from a shared store: the same five worktrees cost ~250 MB total, and a fresh install is 4s. What changed beyond the mechanical rename: - `overrides` moved to `pnpm-workspace.yaml`. pnpm 11 does not read the `pnpm` field in package.json *or* npm's top-level `overrides`, and it fails silently — the vite/defu/language-server pins would have quietly stopped applying. - Build scripts are blocked by default in pnpm; esbuild and sharp are allowed explicitly via `allowBuilds` (renamed from `onlyBuiltDependencies` in 11). - `packageManager` + `engines` pin the toolchain. - gate.sh rejects a package-lock.json/yarn.lock/bun.lock outright, so an agent running `npm install` out of habit fails loudly instead of building a second, divergent dependency tree. - CI bootstraps pnpm with `npm install --global pnpm@11.25.0` rather than corepack (unbundled as of Node 25) or pnpm/action-setup (this self-hosted act-runner has never run a job; fetching a third-party action is not something to discover on the first one). Two pre-existing CI bugs fixed while in the file: - the gate installed with `npm install --package-lock=false`, which discarded the lockfile the previous session had just fixed. - the visual-regression step imported `playwright`, which is not a dependency, and `visual-regression.mjs` has no compare mode anyway — in CI it overwrote its own baselines and passed unconditionally. Removed with a comment; it comes back when it can diff. The `publish` job is now manual (`workflow_dispatch`). During the migration dist/ holds three HTML files against the live pages branch's ten, so publishing on every push to main would take the site down to a stub. Restore at task 20. HANDOVER.md's incident log still says npm where it describes what happened at the time; that is history, not a missed rename. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
18 lines
671 B
YAML
18 lines
671 B
YAML
# pnpm 11 no longer reads the "pnpm" field in package.json; every setting that
|
|
# used to live there (and npm's top-level "overrides") belongs here instead.
|
|
# See https://pnpm.io/settings
|
|
|
|
# Was npm's top-level "overrides". These pins are load-bearing: dropping them
|
|
# silently changes the resolved vite/language-server versions.
|
|
overrides:
|
|
'@astrojs/language-server': 2.15.0
|
|
defu: 6.1.7
|
|
vite: 6.2.1
|
|
|
|
# pnpm blocks dependency postinstall scripts by default. Astro's build needs
|
|
# both of these: esbuild verifies its platform binary, sharp its libvips
|
|
# prebuild. Anything not listed here stays blocked, which is the point.
|
|
allowBuilds:
|
|
esbuild: true
|
|
sharp: true
|