Member-only story
I Finally upgraded to Angular 15. It didn’t go well!
Finally almost a year after Angular 15 was released I finally got around to upgrading our SaaS applications from Angular version 14 to 15. Our applications are big and complex so I knew it wouldn’t be a simple or easy process but I didn’t expect it to go as bad as it did!

First I opened up the trusty Angular upgrade guide I truly wished more frameworks and tools provided something like this! and I got started. Updated NodeJS and Typescript ticked the first few tasks off the list. Everything is going great and then boom. My first issue.
We use NX Workspace for my UI applications as there are a few of them and we didn’t want to have to duplicate logic (more on that in another article). NX Workspace doesn’t allow you to, or at least not without a warning, and suggests you use a different command, use ng update
so I solider on and use the command the nx cli suggests FORCE_NG_UPDATE=true ng update @angular/core@15 @angular/cli@15
✖ Migration failed: Incompatible peer dependencies found.
Let's be honest, in the real world people aren’t keeping their packages up to date and avoiding peer dependency issues, we all wished we were but we aren’t. So try again but this time with the — force
flag.
Keeping a codebase updated with the latest changes in your framework…