Skip to content

compiler: regenerate package-lock.json so npm ci passes again - #43

Closed
ryansolid wants to merge 1 commit into
mainfrom
claude/project-thread-rtxj3o-lockfile
Closed

ryansolid wants to merge 1 commit into
mainfrom
claude/project-thread-rtxj3o-lockfile

Conversation

@ryansolid

Copy link
Copy Markdown
Member

Requested by Ryan · project thread

Every compiler build job now fails at npm ci, on main too (see #42): "package.json and package-lock.json … are not in sync. Missing: @reactivescript/compiler-darwin-arm64@0.1.0 from lock file". Since the 0.1.0 release those platform packages exist on the registry, so npm resolves the optionalDependencies the lock never recorded.

npm install --package-lock-only records them, and the diff touches only compiler/package-lock.json. Checked locally with npm 10.9: npm ci --dry-run fails on main and passes here.

Watch the next version bump: npm run version moves the optional deps to a version that isn't published yet. The publish job's npm ci runs on npm 10, which tolerated that for 0.1.0, but the lock will need regenerating again once those packages are published.


Generated by Claude Code

…ckages

Since 0.1.0 the @reactivescript/compiler-<platform> packages are on the
registry, so npm resolves the optionalDependencies the lock never recorded
and `npm ci` refuses the lock as out of sync: every compiler build job
fails at its first step, on main too. `npm install --package-lock-only`
records them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117BoWPJ3SHHnqKDEZWuteB
@ryansolid ryansolid self-assigned this Nov 10, 2026
@ryansolid ryansolid closed this Nov 10, 2026
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.

2 participants