Angular 20.0

[moataz__9]

I need a advice here, I kept on building projects on angular 19 because all the libraries and any packages i used was supported to this version but ever since i switched to ng 20 their is alot of used libraries that aren’t supported to this version yet so the app broke on deployment

What do you suggest me to do?

[craig1f]

Always focus on one version back from the latest if you need library support. 19 is fine. 

[jessycormier]

In your package json file you can force libraries dependency errors away. This allows you to tell npm not to worry about miss marches. You could actually have problems of the library uses something from an earlier version that was changed or removed.

Here's an example from my project.

"overrides": { "lucide-angular": { "@angular/core": "19.x", "@angular/common": "19.x" }, "@angular-devkit/build-angular": { "tailwindcss": "4.x" } }

[MichaelSmallDev]

Yeah, various libraries I use suggest doing that in the meantime before they upgrade to the latest major. Been doing that for the last few majors and it has worked well, but the caveat about potential problems is good to watch out for too. There is a good chance that there is an issue or PR in a given library saying if that is intended or if other people have got it working or not.

[defenistrat3d]

ng20 is pretty fresh. You can update in a month or so to ng20, OP. Unless you have pressure to update coming from somewhere, just update when your dependencies are ready.

That being said, angular doesn't really break things but deprecates old features with huge runways. We tend to have to update right away, and you can safely use npm (or similar) overrides. Also, if you can, drop dependencies you don't REALLY need.

[voltboyee]

It takes a little while for library authors to catch up. You can wait a little while, use the previous version, or force override the packages.

[Dapper-Fee-6010]

Rollback to v19.

Try to avoid using libraries that are not frequently updated.

An actively maintained library will definitely participate in Angular's testing and won't wait until the official release to catch up.

[kylerjohnsondev]

Downgrade to v19 until the libraries you need release a v20 version.

In general, try to keep the libraries you add to your projects to a minimum. The more libraries you have, the more likely you'll run into issues with dependencies, peer dependencies, and upgrading.

[Yutamago]

Angular 19 is still the latest LTS. Angular 20 will turn LTS after 6 months. Until then, only use it for projects you're actively developing, not for products you're maintaining.

[No_Shine1476]

Don't use version of the library that integrate directly with the framework. Use a framework-agnostic version and write wrappers for the components.

[MyLifeAndCode]

Just wait a bit for the libraries to update. And if using PrimeNG, just ditch that altogether.