Repository navigation
build(deps): update angular to v22 - #3632
Merged
Merged
Conversation
This was referenced Oct 12, 2026
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
TypeScript 6 breaks the legacy module-resolution setting used by two CI test suites.
1 open finding
What changed in this PR
Completes the stacked Angular 22 upgrade for the web UI.
Changes:
- Upgrades Angular, Material, CLI, ESLint tooling, and TypeScript.
- Updates the UI toolkit and Monaco editor integrations.
- Adopts Angular 22’s OnPush and fetch defaults.
| File | Description |
|---|---|
package.json |
Updates framework, tooling, toolkit, and editor dependencies. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Oct 12, 2026
rsdmike
added this pull request to stack #3635
October 12, 2026 23:03
madhavilosetty-intel
previously approved these changes
Oct 13, 2026
rsdmike
force-pushed
the
build/upgrade-angular-22
branch
2 times, most recently
from
October 13, 2026 15:36
82bd20d to
f641c2a
Compare
Update Angular, the CLI and Angular Material from 21.2 to 22.2 with ng update, along with angular-eslint 22.5 and TypeScript 6.0, which Angular 22 requires. ngx-monaco-editor-v2 moves to 22.0 to accept Angular 22, and monaco-editor to 0.56 to satisfy the editor. Components now use the OnPush default and HttpClient the fetch backend. The opt-outs ng update adds for both (ChangeDetectionStrategy.Eager and withXhr) are left out. @device-management-toolkit/ui-toolkit-angular moves to 12.0, the first release built with Angular 22.
TypeScript 6 rejects the options the Cypress node tests pass to ts-node: moduleResolution "node" is deprecated, and an explicit rootDir is required because the compiled sources sit below the tsconfig directory. Use bundler resolution and set rootDir to the project root.
rsdmike
force-pushed
the
build/upgrade-angular-22
branch
from
October 13, 2026 15:45
f641c2a to
f410ec2
Compare
graikhel-intel
approved these changes
Oct 13, 2026
|
🎉 This PR is included in version 3.70.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 3.70.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Updates Angular, the CLI and Angular Material from 21.2 to 22.2 with
ng update, along with angular-eslint 22.5 and TypeScript 6.0, which Angular 22 requires. ngx-monaco-editor-v2 moves to 22.0 to accept Angular 22, and monaco-editor to 0.56 to satisfy the editor.Components now use the OnPush default and HttpClient the fetch backend. The opt-outs
ng updateadds for both (ChangeDetectionStrategy.EagerandwithXhr) are left out.@device-management-toolkit/ui-toolkit-angularmoves to 12.0, the first release built with Angular 22.PR Checklist
What are you changing?
Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. device-management-toolkit/repo#365 )
device-management-toolkit/ui-toolkit-angular#2661