Fix ESLint 10 peer dependency conflict with typescript-eslint #39
+208
−204
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.
The ESLint 10 upgrade broke CI builds because
typescript-eslint@8.54.0only supports^8.57.0 || ^9.0.0, causingnpm cito fail with peer dependency conflicts.Changes
.npmrcwithlegacy-peer-deps=trueto bypass peer dependency resolution until typescript-eslint releases ESLint 10 support (tracked in typescript-eslint/typescript-eslint#11952)package-lock.jsonwith the new npm configurationThis is a temporary workaround documented inline. Once typescript-eslint supports ESLint 10, the
.npmrcfile should be removed.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.