Fix npm peer dependency resolution in CI workflow#1573
Open
RFOF-NETWORK wants to merge 3 commits into
Open
Conversation
Author
|
chore(ci): use npm ci --legacy-peer-deps to fix peer dependency resolution |
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.
Summary
This update modifies the CI workflow to use the command:
npm ci --legacy-peer-depsinstead of the default
npm ci.Reason for change
The previous configuration caused npm to fail when resolving peer dependencies,
especially in environments using strict dependency trees (npm v7+).
By adding the
--legacy-peer-depsflag, the workflow now installs all packageswithout breaking due to peer dependency conflicts.
Impact
and stabilizes automated builds across forks and pull requests.
Verification
The workflow was tested in a forked environment and confirmed to pass all steps.
All checks are now green.