diff options
| author | soryu <soryu@soryu.co> | 2026-05-02 16:50:06 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-05-02 16:50:06 +0100 |
| commit | 2c3b0e3926b8c535fb610092301f8621440b51ed (patch) | |
| tree | e09e3cfde2678de5c972f0964c4dfbe8f13a66f8 /.github | |
| parent | 5b00a6a91aa8c876e042aca123e053b1e8a4ee99 (diff) | |
| download | soryu-2c3b0e3926b8c535fb610092301f8621440b51ed.tar.gz soryu-2c3b0e3926b8c535fb610092301f8621440b51ed.zip | |
fix(frontend): regenerate pnpm-lock.yaml as v6 format + pin packageManager (#123)
Build env's pnpm warned "Ignoring not compatible lockfile" against the v9
lockfile produced by my last regen — older pnpm (8.x and below, which
some build images still ship) only understands v6 lockfiles, and falls
back to "no lockfile" mode which then errors under --frozen-lockfile:
WARN Ignoring not compatible lockfile at /app/pnpm-lock.yaml
ERR_PNPM_NO_LOCKFILE Cannot install with "frozen-lockfile" because
pnpm-lock.yaml is absent
Two-pronged fix:
1. Regenerate the lockfile in v6 format using pnpm 8.15.4 via corepack
(`corepack pnpm@8.15.4 install`). The lockfile now starts with
`lockfileVersion: '6.0'` again — readable by both old and new pnpm.
2. Pin `packageManager: "pnpm@8.15.4"` in package.json so build envs
that respect corepack/Volta install the right version automatically
instead of falling back to whatever's globally installed.
Verified locally with `corepack pnpm@8.15.4 install --frozen-lockfile`
(the CI command). \`tsc --noEmit\` passes.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions