Fix npm dependency conflict in wrongsecrets-balancer/ui by adding .npmrc #990
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.
Problem
Running
npm installin thewrongsecrets-balancer/uidirectory failed with an ERESOLVE peer dependency conflict:The root cause is that
[email protected]expects TypeScript 3.x or 4.x, but the project uses TypeScript 5.9.2, creating a peer dependency mismatch.Solution
Added
.npmrcfile inwrongsecrets-balancer/uiwithlegacy-peer-deps=trueto instruct npm to use the legacy peer dependency resolution algorithm, which allows the installation to proceed despite the version mismatch.This approach:
npm ci --legacy-peer-depson line 11Verification
All tests and builds pass successfully:
npm installcompletes without errorsnpm ciworks correctlynpm run buildproduces optimized production buildFixes the issue reported where developers were unable to install dependencies locally.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.