An Angular modernization checklist: from NgModules to standalone, signals and zoneless
The practical decision
Change one boundary, verify the user journey and keep a way back.
A useful modernization makes the next feature easier to deliver. This checklist separates framework upgrades from state, forms and architecture changes so that each stage has a clear result. Adapt the order to the application and its dependencies.
0. Define the outcome
Start with the problem: an unsupported dependency, slow delivery or a screen that is hard to change. Agree on the target version, affected journeys and acceptance checks. Choose framework features because they help that outcome.
1. Protect the working behaviour
Record a critical user journey before changing it. Cover loading, success, empty results and failure. Investigate unstable tests and keep a fast check for each stage. Coverage helps locate gaps; a percentage alone cannot show that a feature works.
2. Make dependencies explicit
Introduce TypeScript strictness and strictTemplates in manageable areas. Use lint rules to enforce which modules may depend on which. This makes later moves safer and exposes product code that has drifted into shared libraries.
3. Upgrade the framework separately
Follow the official update guide one major version at a time. Check the supported Node.js, TypeScript, RxJS and third-party library versions at each step. Keep a test-runner migration separate from the framework upgrade so failures have a clear cause.
4. Migrate composition
Run the standalone migration in its documented stages: convert declarations, remove unnecessary modules, then change bootstrap. Check lazy routes, providers, guards and resolvers. When adopting @for, use stable record IDs for editable or reordered lists so focus and input state follow the right row.
5. Choose state tools by purpose
Use signals for synchronous state and computed() for derived values. Keep RxJS where cancellation, debouncing or combined streams help. Signal inputs and queries can be migrated independently; output() emits events and is not a signal. Review skipped migrations before calling a stage complete.
6. Check what triggers rendering
Exercise external callbacks, programmatic form updates and hosted components. A signal read by the template, AsyncPipe or markForCheck() can notify Angular. OnPush compatibility is useful preparation for zoneless operation, but switching the strategy alone does not prove the application works.
7. Verify zoneless behaviour
Follow the configuration for your target Angular version and test the same mode in TestBed. Check late responses, timers and non-Angular event sources. Let scheduled rendering complete with fixture.whenStable() where appropriate; forcing a render after every state change can conceal a missing notification.
8. Keep form changes scoped
Preserve validation, disabled state, focus and submission behaviour. Reactive Forms remain a valid choice. Consider Signal Forms when their API fits the form and the target version. Treat a form rewrite as its own change with observable acceptance criteria.
9. Extract demonstrated reuse
Move shared behaviour behind a stable contract when consumers justify it. Nx can coordinate projects, enforce boundaries and run affected checks. It is a workspace choice, not a prerequisite for modernization. The shared UI notes explain how to keep product rules outside a library.
10. Release a stage your team can maintain
Keep each stage independently reviewable and revertible. Record the decision, the tested revision and any remaining limits. The handover should explain how to make the next change.
Example: one search screen
Convert the screen to standalone, then migrate local filter state separately. Retain the RxJS pipeline that cancels obsolete searches. Verify that a slow previous response cannot replace the latest result and that loading, errors and selection still work.
ClearCraft Geoportal shows my approach to Angular architecture and delivery. It is an independent product, not a before-and-after client migration or a promise of a particular migration time.