chore: upgrade to Angular 22 - #660
Open
agrahari-himanshu wants to merge 8 commits into
Open
agrahari-himanshu wants to merge 8 commits into
agrahari-himanshu wants to merge 8 commits into
Conversation
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…quisites Angular 22's compiler-cli requires TypeScript >=6.0 <6.1, and @angular-eslint v22 only supports ESLint 9 flat config. Bumping these first, ahead of the Angular package update, satisfies peer dependency checks so `ng update` can proceed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Runs `ng update`'s automated migrations: annotates existing components with ChangeDetectionStrategy.Eager to preserve pre-v22 change detection defaults, and suppresses the new strict template extended diagnostics to keep prior compile behavior. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…olver TypeScript 6.0 flips the "strict" default to true; explicitly set strict: false to preserve this project's pre-upgrade (non-strict) compiler behavior instead of chasing strictness errors across the whole codebase. Also silence the now-blocking baseUrl deprecation warning, exclude e2e/** and enable skipLibCheck in the demo's tsconfig.spec.json (its root-level "**/*.spec.ts" include was accidentally pulling in Playwright e2e specs and playwright-core's type declarations). Angular 22 removes ComponentFactoryResolver; DatePickerDirective now creates DatePickerComponent directly via ViewContainerRef.createComponent(), which Ivy has supported since Angular 13 and is behavior-equivalent to the old factory-based API. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
--watch=true made this script hang forever instead of exiting after a single run, so it never actually verified anything in CI. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@angular-eslint v22 only supports ESLint 9 flat config; the legacy .eslintrc.json format is no longer read. Ported the existing rules 1:1 into eslint.config.js using the angular-eslint/typescript-eslint umbrella packages (dp-prefixed selectors, no-output-native/on-prefix off, prefer-standalone warn, no-console/no-debugger, single quotes). angular-eslint v22's tsRecommended preset newly includes prefer-inject and prefer-on-push-component-change-detection as errors; disabled both to keep lint at its pre-upgrade baseline (0 errors) rather than force a DI/change-detection style rewrite across the whole library as a side effect of this upgrade. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…leanup - Bump ng2-date-picker library version and peerDependencies (@angular/common, @angular/core, @angular/cdk) to ^22.0.0. - Add engines.node >=22.0.0 to package.json to make the new Angular 22 floor explicit. - Bump the stale rxjs devDependency from ^6.5.3 to ^7.8.0 to match the version Angular's own deps already resolve to. - Remove the orphaned ng2-date-picker-demo-e2e project from angular.json: it used the removed protractor builder with no protractor.conf.js on disk, dead since the v17 Playwright migration, and wasn't exercised by any npm script. - Update README's stale "Supports latest (Angular 15)" line and add a CHANGELOG entry for the 22.0.0 release. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
vite@8.1.5 (pulled in transitively via @angular/build) requires @types/node "^20.19.0 || >=22.12.0" as a peer dependency, but the root package.json still pinned ^18.15.3. npm 11 tolerated the mismatch, but npm 10 (bundled with actions/setup-node's Node 22) resolves a separate @types/node@26.6.1 to satisfy the peer that never made it into the committed lock file, causing `npm ci` to fail with EUSAGE in CI. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Closes #659
Summary
npm cifailure by bumping@types/nodeto satisfy vite's peer rangeTest plan
🤖 Generated with Claude Code