Repository navigation
Conversation
…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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Ryan · project thread
Every
compilerbuild job now fails atnpm ci, onmaintoo (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 theoptionalDependenciesthe lock never recorded.npm install --package-lock-onlyrecords them, and the diff touches onlycompiler/package-lock.json. Checked locally with npm 10.9:npm ci --dry-runfails onmainand passes here.Watch the next version bump:
npm run versionmoves the optional deps to a version that isn't published yet. The publish job'snpm ciruns 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