How to handle a devDependency that has not yet released a version compatible with a new...

I am upgrading my Angular project from Angular 19 to Angular 21.

During the upgrade, one of my devDependencies (jest-preset-angular) has not yet released a version compatible with Angular 21. As a result, npm install fails with peer dependency conflicts.

The error is as follows:


I want to complete the framework upgrade without breaking the build, but also avoid introducing long-term technical debt.

Final question

What is considered the best practice in situations where a devDependency has not yet caught up with the latest Angular version?

Continue reading...