build: move engineStrict and saveExact to pnpm-workspace.yaml (13-09)

pnpm 11 ignores these keys in .npmrc, so installs on an unsupported Node
succeeded and new dependencies were saved with a ^ range. pnpm config now
reports both as true.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
DongHyeonka
2026-09-25 23:14:13 +09:00
co-authored by Claude Opus 5.5
parent 4add908c65
commit a5dc851e0d
2 changed files with 7 additions and 2 deletions
+2 -2
View File
@@ -1,2 +1,2 @@
engine-strict=true
save-exact=true
# pnpm 11 reads engineStrict and saveExact from pnpm-workspace.yaml, not from
# this file (review 13-09). Keep only npm-level settings such as registry auth here.
+5
View File
@@ -1,3 +1,8 @@
# 13-09. pnpm 11 ignores these keys in .npmrc (`pnpm config list` did not show
# them), so an unsupported Node version installed and new dependencies were
# saved with a ^ range. pnpm 11 reads its settings from this file.
engineStrict: true
saveExact: true
allowBuilds:
esbuild: true
msw: true