Upgrade to Angular 22 when 23 comes out
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 0
- Avg merge
- 20h 8m
- Merged PRs (30d)
- 30
Description
**Describe the task**
We want to be one version behind the latest version of Angular.
**Purpose**
I don't think we should upgrade to 22 as soon as it comes out, because it takes some time to stabilize and for all the associated packages to catch up. It might be good to be like 1 version behind. Like when 23 comes out, upgrade to 22.
**Acceptance Criteria**
- [ ] ALCS frontend
- [ ] Angular 22
- [ ] Jest ___
- [ ] `@angular-builders/jest` ___
- [ ] Portal frontend
- [ ] Angular 22
- [ ] Jest ___
- [ ] `@angular-builders/jest` ___
Confirm this task meets our team [**Definition of Ready (DoR)**](https://www.figma.com/board/XmNkN600aAVWFCBmSDdt10/Team-Documents?node-id=1-2&t=Xjd6nHZZ7YlnoOrD-4) before moving to the **Next Sprint** column.
Confirm this task meets our team [**Definition of Done (DoD)**](https://www.figma.com/board/XmNkN600aAVWFCBmSDdt10/Team-Documents?node-id=3-21&t=Xjd6nHZZ7YlnoOrD-4) before moving to the **Done** column.
Contributor guide
No contributing guide indexed for this repository
Research direction
Begin with the dependency configuration for the ALCS and Portal frontends; the issue names no specific files. Check Angular 22, Jest, and @angular-builders/jest compatibility, then run both frontend test suites and builds. Done means both frontends satisfy every Angular 22 and Jest acceptance item.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100