Skip to content

Fix npm peer dependency resolution in CI workflow#1573

Open
RFOF-NETWORK wants to merge 3 commits into
microsoft:mainfrom
QCH-L-C:main
Open

Fix npm peer dependency resolution in CI workflow#1573
RFOF-NETWORK wants to merge 3 commits into
microsoft:mainfrom
QCH-L-C:main

Conversation

@RFOF-NETWORK

Copy link
Copy Markdown

Summary

This update modifies the CI workflow to use the command:
npm ci --legacy-peer-deps
instead 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-deps flag, the workflow now installs all packages
without breaking due to peer dependency conflicts.

Impact

  • CI builds now run successfully without ERESOLVE errors.
  • Tests, linting, and container builds proceed as expected.
  • This change ensures compatibility with existing dependency versions
    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.

@RFOF-NETWORK

Copy link
Copy Markdown
Author

chore(ci): use npm ci --legacy-peer-deps to fix peer dependency resolution

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