ci: use npm install to avoid npm ci optional-dependency bug (rollup native binary) - #13
Merged
Conversation
…4828) with rollup native binary
Luckycat133
enabled auto-merge (squash)
July 28, 2026 06:40
…all on CI (use npm install)
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
1 participant
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.
Workaround for npm/cli#4828:
npm ciintermittently fails to install the platform-specific rollup native binary (@rollup/rollup-linux-x64-gnu), breakingnpm test/npm run buildon GitHub-hosted runners. Switching tonpm installresolves optional deps fresh and installs the native binary reliably.