Repository navigation
Fix code-quality CI: resolve npm peer conflict from TypeScript 7 bump - #287
Merged
smokhov merged 1 commit intoOct 2, 2026
Conversation
Co-authored-by: smokhov <10067003+smokhov@users.noreply.github.com>
smokhov
added this pull request to stack #288
October 2, 2026 20:11
Copilot created this pull request from a session on behalf of
smokhov
October 2, 2026 20:11
View session
smokhov
marked this pull request as ready for review
October 2, 2026 20:12
smokhov
approved these changes
Oct 2, 2026
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.
npm ciinsrc/java/ws/rest-clientfails in thecode-quality (22.x)job. The TypeScript 7.0.2 bump conflicts with the peer rangetypescript >=6.0 <6.1that the Angular build tooling declares.This PR does not move TypeScript up. It pins
typescriptto~6.0.3and updates the surrounding dependencies. TypeScript 7 cannot be adopted with current releases, so this is a stopgap until upstream support lands.Why 7.x isn't viable yet
@angular/compiler-cli,@angular/buildand@angular-devkit/build-angular(latest 22.2.1, and22.3.0-next.0) all declaretypescript >=6.0 <6.1.typescript-eslintcaps at<6.1.overridesentry fortypescriptletsnpm installsucceed, but both tools then fail at runtime:ng build:Cannot read properties of undefined (reading 'Error')ng lint:Cannot read properties of undefined (reading 'Intrinsic')@typescript/typescript6for the tooling viaoverridesdoesn't work either. npm requires the root package to satisfy each peer dependency.package.jsonandpackage-lock.jsontypescript:~7.0.2→~6.0.3@angular/*and@angular-devkit/build-angular: aligned to^22.2.1. This also fixes a@angular/common22.1.1 vs@angular/corepeer mismatch.angular-eslint:22.1.0→^22.5.0typescript-eslint:8.65.0→^8.71.0Follow-up: move to TypeScript 7 once Angular and
typescript-eslintpublish versions that support it.