Initial hypothesis ("pnpm@latest pulled a newer 11.4+ with new Node
floor") was wrong. Investigation after the second VPS crash showed
the whole pnpm 11.0+ line imports node:sqlite from its store-index
module. Local dev was misleading because pnpm install never re-ran
on the Node 20 host (lockfile already resolved, child scripts don't
load the store module).
Updates:
- BLK-005: replace single-fix line with iteration log
(@latest → @11.1.3 → @10.13.1, last one resolved).
- LRN-022: rewrite headline + body to reflect pnpm 11 ↔ Node 22.13
coupling, not just pnpm 11.4. Add pnpm/Node compat matrix.
- journal 2026-05-21: append v2 fix entry referencing commit 990c8e7.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- BLK-005: VPS Docker build crash on pnpm@latest pulling pnpm >=11.4
needing Node 22.13 (node:sqlite import) against node:20-alpine image.
Resolved by pinning pnpm@11.1.3.
- LRN-022: never use floating pnpm@latest (or any unpinned upstream
tag) in Dockerfiles — pnpm minor bumps can silently raise Node floor.
Fix paths: pin exact + mirror in packageManager field; audit CI too.
- journal 2026-05-21: two lines for the rename commit and the Docker
pin commit.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>