build(deps): update workspace to Angular 22#341
Merged
Conversation
Add ^22.0.0 to the @angular/common and @angular/core peerDependencies so the package installs on Angular 22 without emitting peer-dependency warnings. https://claude.ai/code/session_01Pki7QYb67QhVAnqeX2fjg4
Drop the 'release candidate'/@rc wording (v5 is stable), replace the GenericTableCoreModule NgModule quick-start with standalone CoreComponent usage, and remove the webpack-era '~' scss import prefix. https://claude.ai/code/session_01Pki7QYb67QhVAnqeX2fjg4
|
🎉 This PR is included in version 5.1.1 🎉 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
2 participants
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.
Summary
Upgrades the workspace from Angular 21 to Angular 22 via the official
ng updateflow, plus the necessary follow-ups and a docs refresh.Dependency upgrade
ng update @angular/core@22 @angular/cli@22— all@angular/*,@angular-devkit/build-angular,@angular/compiler-cli, andng-packagrto22.0.0.@analogjs/vite-plugin-angular/@analogjs/vitest-angular→^2.6.0(older peer range excluded Angular 22).enginesNode floor to^22.22.3(Angular CLI 22 minimum).Migration follow-ups
"ignoreDeprecations": "6.0"to the root tsconfig — TS 6.0 now errors onbaseUrl/downlevelIteration; removingbaseUrlwould have broken the docs app'spathsresolution.core.component.htmlby unwrapping$safeNavigationMigration(transform?.args)totransform.args(transformis guaranteed truthy in those templates, matching the existingtransform.pipeusage).ChangeDetectionStrategy.Eagerto docs example components andwithXhr()toprovideHttpClient.Library compatibility (
fix(core))^22.0.0to the core library's@angular/common/@angular/corepeer dependency ranges so installs on Angular 22 don't emit peer warnings. This is thefix(core)commit that will trigger a patch release on merge.Docs
README.md: dropped stale "release candidate"/@rcwording, switched the quick-start to standaloneCoreComponentusage, and removed the webpack-era~scss import prefix.Verification
npm run build(core library) ✓npm test— 171/171 passing ✓npm run build:docs(production) ✓Release impact
The
fix(core):commit will cause semantic-release to cut a patch release (e.g.5.1.0 → 5.1.1) when this merges tomain. The Angular 22 workspace upgrade and docs changes are release-neutral (build/docs).https://claude.ai/code/session_01Pki7QYb67QhVAnqeX2fjg4
Generated by Claude Code