feat: add Angular 22 support - #3741

The change is ready and locally validated, but the Test and publish workflow is currently marked action_required before any jobs start because this fork needs maintainer approval to run Actions. Could a maintainer approve the workflow run when convenient? Thank you.

The change is ready and locally validated, but the Test and publish workflow is currently marked action_required before any jobs start because this fork needs maintainer approval to run Actions. Could a maintainer approve the workflow run when convenient? Thank you.

Have you tried the "actions" tab at your forked repository? I believe you can run those workflows over there if you want to try out the "test and publish" workflow :)

Hi @EthanSK, thanks for this, and sorry for the long silence. I am the new maintainer, and this PR was triaged the day it opened but then held while we got 21.0.0-rc.1 out. That release is on npm now, so I can give you a real answer.

Here's what I found:

What your PR already gets right

• reflectComponentType(component)?.selector is the correct replacement for the removed ComponentFactoryResolver, in both screen-tracking services.
• The src/test.ts zone.js imports have to move to zone.js, zone.js/testing and zone.js/plugins/task-tracking. TypeScript 6 now errors on the old paths, where 5 ignored them.
• The two prefer-optional-chain fixes and the Node matrix change are needed as is.

What changed since you submitted this PR

• main moved to Angular 21.2 and firebase 12.18, so package.json, src/package.json and the lockfile now conflict.
• ng-packagr 22.2 switched its typings bundler, and the build now fails on src/compat/storage/observable/fromTask.ts until that function gets an explicit return type.
• src/package.json on main now declares "type": "commonjs", which makes the new src/schematics/package.json in the PR unnecessary.
• We keep the version field at the last released version and let tags drive publishing, so the move to 22.0.0-rc.0 would need to come out.

Where this goes next

I cannot merge any Angular 22 change into main yet, because every merge there publishes a canary and 21.0.0 has not been tagged. The plan is to cut a 21.0.x branch for the 21.0.0 release shortly and open main to Angular 22 work right after that. I will post the details on #3696 once the branch exists.

So two ways forward, and I am fine with either:

• You refresh this branch against main once I post that the 21.0.x branch is cut, and I review it then.
• I fold your changes into a fresh pull request, with you as co-author on the commit and credited in the release notes, and link it from here before closing this one.

Let me know which you prefer. If I do not hear back by October 14, I'll go ahead with the second option and say so here. Either way, thank you for getting this started months before I could.