Skip to content

fix(deps): regenerate lockfile so npm ci works on node:20 - #50

Merged
oratis merged 1 commit into
mainfrom
fix/lockfile-swc-nested
Aug 1, 2026
Merged

fix(deps): regenerate lockfile so npm ci works on node:20#50
oratis merged 1 commit into
mainfrom
fix/lockfile-swc-nested

Conversation

@oratis

@oratis oratis commented Aug 1, 2026

Copy link
Copy Markdown
Owner

npm ci on node:20-alpine (npm 10) rejected the lock: next-intl's @swc/core needs @swc/helpers >=0.5.17 but only next's hoisted 0.5.15 was recorded. Pre-existing on main — npm 11 tolerates it as invalid, and no image had been built from main since 07-04. Regenerated; both copies now recorded. tsc + build clean. 🤖 Generated with Claude Code

The image builds on node:20-alpine, whose npm 10 rejected the lock with
"Missing: @swc/helpers@0.5.23". Root cause is unrelated to any recent feature
work: next-intl pulls @swc/core, which requires @swc/helpers >=0.5.17, but the
tree hoisted next's 0.5.15 to the top and no nested copy was recorded. npm 11
(local) flags that as `invalid` yet installs anyway, so it never surfaced —
and no image had been built from main since 2026-07-04, so CI never caught it
either.

Regenerated from scratch: the lock now carries both
node_modules/@swc/helpers@0.5.15 (next) and
node_modules/next-intl/node_modules/@swc/helpers@0.5.23 (@swc/core), and
`npm ls @swc/helpers` reports no invalid resolutions. next-intl moved 4.13.0 →
4.13.4 within its existing semver range. tsc and next build are clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@oratis
oratis merged commit e953908 into main Aug 1, 2026
@oratis
oratis deleted the fix/lockfile-swc-nested branch August 1, 2026 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant