Member-only story

I Finally upgraded to Angular 15. It didn’t go well!

Brad Beighton
ITNEXT
Published in
6 min readAug 9, 2023

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!

A determined developer — generated by AI

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…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Published in ITNEXT

ITNEXT is a platform for IT developers & software engineers to share knowledge, connect, collaborate, learn and experience next-gen technologies.

Written by Brad Beighton

I am a Solution Architect for a global workplace management SaaS product. I craft innovative solutions that enhance productivity and user experiences.

Responses (7)

What are your thoughts?

Got through that pain. Upgrading a classic Angular project with NX (MHO) is not the path. What worked for me was creating a whole new NX workspace to contain my Angular projects, recreate the projects and then copy & paste the source files. Besides…

2

Diligently crafted post – kudos!

1

We do monthly releases so I try to upgrade to latest at the start of each development period. I do Angular and big libraries like AG Grid and Dev Extreme. Takes about 30 minutes. Now perhaps a few might think I'm crazy staying that up to date and…

2

Recommended from Medium

Lists

See more recommendations