diff options
| author | soryu <soryu@soryu.co> | 2026-05-02 16:33:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-05-02 16:33:51 +0100 |
| commit | 5b00a6a91aa8c876e042aca123e053b1e8a4ee99 (patch) | |
| tree | 0276c472981313a1e44636a8fca866ddadf9ca9b /makima/frontend/package.json | |
| parent | 08d2ea6a685e248146b30f70421b853ff404b9ad (diff) | |
| download | soryu-5b00a6a91aa8c876e042aca123e053b1e8a4ee99.tar.gz soryu-5b00a6a91aa8c876e042aca123e053b1e8a4ee99.zip | |
fix(frontend): regenerate corrupted pnpm-lock.yaml (#122)
The committed lockfile was a manual frankenstein of pnpm v6 metadata
(`lockfileVersion: '6.0'` + `resolution:` blocks at the top) and v9-style
snapshot entries appended below. pnpm 9 read it as a single packages: map
and tripped on duplicate mapping keys (\`@floating-ui/core@1.7.5\` appeared
twice; same for \`@floating-ui/utils@0.2.11\`, plus dozens of \`@lexical/*\`
and \`@babel/*\` entries duplicated across the v6/v9 sections).
This blew up Docker / Caddy builds:
ERR_PNPM_BROKEN_LOCKFILE The lockfile at "/app/pnpm-lock.yaml" is broken:
duplicated mapping key (688:3)
Regenerated with \`pnpm install --no-frozen-lockfile\` against the existing
package.json — net -1605 / +545 lines. \`pnpm install --frozen-lockfile\` now
succeeds (the CI check), \`tsc --noEmit\` passes, \`vite build\` produces a
clean bundle.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Diffstat (limited to 'makima/frontend/package.json')
0 files changed, 0 insertions, 0 deletions