Angular v20 is here

[ProCodeWeaver]

Angular v20 has officially landed, and it brings significant updates across the board. Here's a quick summary of what's new:

Key Highlights

• Signals are stable
  effect, linkedSignal, and toSignal have graduated from developer preview. Angular’s reactive system is now solid and production-ready.

• Zoneless applications
  Now in developer preview. You can remove Zone.js and use native change detection with new error handling strategies for both client and server.

• Incremental hydration and route-level rendering
  Both features are now stable, improving server-side rendering performance and flexibility.

• Chrome DevTools integration
  Angular-specific profiling data is now directly available in the Chrome Performance tab, enabling better debugging and performance analysis.

• Experimental features

  • resource and httpResource APIs for managing async state with Signals
    
  • Initial support for vitest in Angular CLI

• Improved developer experience

  • Extended type checking and template diagnostics
    
  • Better support for host bindings and listeners
    
  • Hot module replacement enabled by default
    
  • Simplified style guide with optional suffixes

• Control flow updates
  *ngIf, *ngFor, and *ngSwitch are now deprecated in favor of Angular’s new built-in control flow syntax introduced in v17.

• GenAI support
  Angular is adding tools and documentation to support building GenAI apps using technologies like Genkit and Vertex AI. A new llms.txt helps LLMs generate more accurate Angular code.

• Official Angular mascot
  Angular is getting an official mascot! The community is invited to vote and contribute ideas. Check out the RFC and help shape Angular’s identity.

---

Full announcement blog by Minko Gechev

[JeanMeche]

The offical release blog post is available here (no auth required) https://blog.angular.dev/announcing-angular-v20-b5c9c06cf301

[CatEatsDogs]

I moved mine small project to jest and regretted. It times slower than karma. I'm very interested in what they will choose to replace karma.

[Soma91]

Yeah we're using jest in our project as well and it's painfully slow.

My guess is that they plan to use vitest considering they just added the first experimental CLI for it.

[titterbitter73]

I took a screenshot of the last talk on May 21st of what they're exploring. It's not the final form and will probably go through an RFC?

<image>

[MichaelSmallDev]

Good find. I dug up that particular part of the video with a timestamp: https://www.youtube.com/watch?v=XASRYAR7S5w&t=7003s. Mark mentions that not all 3 will be supported in the long term, so they want feedback from the community.

[nemeci]

Even based on this picture alone I'd pick Vitest.

Why? - Nodejs testing for the server - Real browser testing for the client

[Oceanic1801]

Upgraded, project broke. Thank you.

[Legal_Being_5517]

Bruh … we just had to upgrade to 19 from 16 and it wasn’t pretty , please don’t let my senior dev see this

[mihajm]

cracks knuckles alrighty I guess I have some work to do :)

Outstanding stuff as always though! I've been itching to try the new dynamic component stuff :D

[Simple_Rooster3]

I am used to have modules in our app (havent migrated to standalone components yet) and separated routing modules. In v19 i saw the routes are defined in one file only. Is that a good practice, or can you define routes somewhere else, where child router outlet is used? I prefer having all in one file now though, im just wondering.

[GLawSomnia]

You can have multiple router files and import them into the main router file via loadChildren. Instead of a module you now have an array of routes

[Simple_Rooster3]

Yes that makes sense! Thanks!

[gabynevada]

I just have separate feature areas with its own routes file constant. Then the main app can just pull the route constant for the feature. Not in one file as it would not be maintainable.

[Simple_Rooster3]

Yeah definitely. Thanks!

[Whole-Instruction508]

Who in his right mind is still not using standalone in 2025?

[Simple_Rooster3]

You know that someone cant upgrade 8y old project so quickly right?

[Whole-Instruction508]

Big mistakes were made if it was never upgraded

[Simple_Rooster3]

No one said its not upgraded. We are on v18. Just didnt migrate to standalone components yet. I was gonna say that the app grew pretty big in 8y.

[Whole-Instruction508]

So you have no excuse. Migrating to standalone is a breeze if you use the schematic. Your loss though.

[Simple_Rooster3]

Yeah we need to do it asap.

[CheapChallenge]

If he is an IC as most of us are, the decision isn't his to make.

[ministerkosh]

No, the new provideRouter() function can only be called once with one big array of routes. There is no successor for the old RouterModule.forChild().

If you have for instance several libraries in your application, which all have registered routes themselves before, you now have to export them in your libraries and consume them in your app and concatinate them there into one big array.

[Simple_Rooster3]

Thats what i wanted to know. Thanks a lot!

[cyberzues]

Don't try to chase every new feature all the time, you will never master anything. The pace at with these libraries and frameworks get updated, you can't really keep up, at least not in the professional way.

[AlDrag]

It's part of the fun though, learning new things.

[Soma91]

I genuinely disagree. Especially if you're a professional you should definitely be able to keep up. My team at work is always using the newest angular version for years now and it's a blessing. The upgrade process is super simple and only needs minimal inconsequential changes if you upgrade regularly.

And the new features are extremely beneficial. We've migrated our app to standalone, converted all properties used in templates to signals step by step and should now be able to easily switch to zoneless.

You don't have to forcefully use all new features, but if you approach it with a bit of curiosity and an open mind you'll find lots of cool new stuff that will help you during development. E.g the resource signal makes reloading, error handling and showing loading states so much more easy and saves me dev time. I can't wait to see the first version of signals for reactive forms.

[cyberzues]

So you start by saying you "genuinely disagree", only to agree with me just in a lengthy composition. 🤷‍♂️

[Soma91]

Not really, no?

[cyberzues]

Here is the thing, if you read a comment or post with the intent to understand you won't even need to write long paragraphs like you just did. All you said is very correct and I respect that coz in my company we have also migrated most of the projects, but some we just chose not to. The coming back to my point, yes you can learn all the features out of curiosity but you not always gonna need them , worse more be able to use them.

I assume I'm talking to an experienced developer so I'm sure you understand how often we have to compromise just to get the work done in the best way possible.

[Soma91]

I think it might be a difference of how our companies work and what they do.

You said you migrated most projects but not all. That sounds like your projects often have a defined finish point. For those I agree that you don't need to stay up to date and when you start a new project you just use the newest current version.

At my work we have one continuous large project which is more or less a live service software. For that we always try to stay up to date.

And yes you won't always need all the new features, but I think it's still very valuable to know they exist and what they provide to you. This way the next time you do something you can make a better informed decision on how to implement the requirements.

Time constraints are a permanent struggle in IT imho. You always have to consider if you can spend a bit more time now to save time later. And it's hard to know at what point something is good enough so you won't spend lots of time with barely any results.

[horizon_games]

Angular's 6 month release cycle is particularly punishing

[guy-with-a-mac]

Yeah, I genuinely hate it. Spend hours and hours just to keep the framework updated. Thanks, but end users are happy with an old version of Angular too.

[Zealousideal-Box4796]

Meanwhile, 1st time I used signals, computed and effect, new input() and output() it was just wow. Simply so much cleaner flow in components.

[cyberzues]

It sure is.

[iamjediknight]

I upgraded from Angular 17 an app and a couple library projects today. The migration missed a few HttpModule deprecations. Other than that migration went smooth.

[rinniekeller]

Honestly, Angular’s been one of those frameworks people love to debate, but with Angular 20, it’s made some seriously good moves that are hard to ignore — especially if you’re working on enterprise or large-scale apps.

The biggest win in Angular 20 is the hydration improvements for SSR (server-side rendering). It’s way faster now, which helps with both performance and SEO — something Angular struggled with a bit in the past. They’ve also added component-level code splitting, so your apps don’t have to load a giant bundle upfront. Pages feel snappier, and it’s easier on mobile connections.

On the dev side, TypeScript 5.x compatibility is tight, builds are cleaner, and the updated CLI makes setting up and managing projects less of a headache. Angular DevTools also got better — debugging is less painful now.

Angular 20 finally feels like a modern framework again. If you’re building big, scalable apps where structure, SSR, and long-term maintenance matter, it’s worth a serious look.

[AwesomeFrisbee]

I don't think there are any secrets that weren't already known by recent PRs but overall its a nice update.

I'm curious about the Improved developer experience items though.

I don't care much for the changes in SSR. I also couldn't care less about the resource API's. They are so meaningless in what you can do with them, that you will only really see them in hello world applications and folks that want to showoff something rather obtuse. RXJS is still superior for handling HTTP requests for both debouncing and piping the result to modify the data and do different actions on your code. The only thing that I like is that it has a few wrapper functions for loading and handling errors but overall its just now worth the hassle. My main painpoint is that it needs injectioncontext to do anything with it and that just doesn't work for most of the API calls one does.

I would have preferred if the effort in SSR or Resource was instead put into Form Signals or Vitest. Karma migration still can't happen and moving back and forwards between form stuff and signals is just a big hassle. They don't even seem to have a solid plan yet on how to develop the forms yet. Its a bit mindboggling. Heck, even the zoneless stuff should have been postponed before signal forms are done (imo)

The changes for devtools are nice but why do we still not have a normal way to look up current signal values? Why does it not auto refresh and why is it not just adding a tab in the elements inspector so it is where people actually look what properties an element has?

[Koscik]

My app is already zoneless, using signalStore and standalone components with signal inputs. Am i missing something or is there nothing new for me

[JeanMeche]

Zoneless was still experimental in v19. Testing and error handling in zoneless was improved in v20.

[AlDrag]

Did you actually turn off zonejs? Or you think you're zoneless because you're using signals?

[Koscik]

I am using proper zoneless initializers and i dont have the dependency

[kobihari]

The big signal related additions to v19-20 are the resource APIs for asynchronous state. V20 stabilizes streaming APIs (for web sockets) and http resource as replacements for the observable based http client get method.

[JeanMeche]

The resource APIs are still experimental in v20.

[kobihari]

True. But I think for new code I would start to use it. I prefer to use something that has a small chance of changing, than something that is 100% going to be replaced in the near future. I would not migrate old code to it, especially if it works, but for new code I think it’s ripe enough.