Several major versions at once
Angular officially supports updates from one major version to the next. Coming from a very old version means walking through every intermediate step – including its migrations.
Is your application several major versions behind the latest Angular release? I bring it up to date – with all mandatory migrations and without your team having to freeze feature work for months.
An Angular upgrade is rarely urgent – until it suddenly is. Every skipped major version makes the next step bigger: dependencies stop fitting together, security updates dry up and new team members learn outdated patterns.
At some point the old version blocks concrete plans – a new library, a current Node.js version in CI, or simply the limited support window Angular gives every major version.
ng update aborts with peer dependency conflictsAngular officially supports updates from one major version to the next. Coming from a very old version means walking through every intermediate step – including its migrations.
Angular, Angular Material/CDK, NgRx, TypeScript, RxJS and Node.js each have their own compatibility ranges. A single unmaintained library can block the entire upgrade.
Pre-Ivy code, removed APIs, deprecated RxJS operators or linting that was never migrated from TSLint create many small issues during the upgrade.
Without reliable unit and end-to-end tests it is hard to verify that everything still works afterwards – so the upgrade is postponed out of caution.
I analyse the starting version, dependencies, build setup and test coverage and define the migration path version by version – including libraries that need replacing or upgrading alongside.
For each major version: ng update with the official schematics, dependency adjustments and manual follow-up where automatic migrations fall short. Every step lands as a traceable commit.
After each intermediate step, build, linting and existing tests must pass. I additionally check critical user flows manually or with end-to-end tests (e.g. Playwright or Cypress).
You receive a mergeable state, short documentation of the changes and pointers to optional modernisation such as standalone components, the new control flow or signals.
On request
Optional migrations – for example to standalone components, the new control flow (@if, @for) or signals – can be quoted separately on request.
I worked with Fabian for half a year and it was a pleasure! His knowledge and expertise helped us create a solid foundation for a new project that we will work on now for years. Communication and transparency was amazing so working with him in our team was a blast!
Not directly: Angular expects updates from one major version to the next. I move through the intermediate versions quickly, though, so you end up on the current version in one go.
It mainly depends on the version jump, the size of the codebase and the third-party libraries in use. After a quick look at your repository I'll give you a binding time frame.
Usually not. I work on a separate branch and keep merging in your team's changes. Only the final merge benefits from a short, agreed time window.
The upgrade to the current Angular version including all mandatory migrations. Optional modernisation such as standalone components or signals is not included and can be quoted separately.
In a free intro call we'll clarify your starting version, dependencies and time frame.