Angular's 2025 strategy focuses on improving the developer experience in general, compatibility with the JavaScript ecosystem. Angular 19.2 will introduce a streaming option for resources, and other updates include Tailwind CSS v4 improvements and Nx's work on reducing TypeScript typechecking time.
Q&A Angular Strategy
A special and quite intensive Q&A session with Mark Thompson and Minko Gechev, who is the product lead for Angular, took place. It was about Angular's strategy for 2025.
It was one question after the other, but the main takeaways, are that is not 100% certain that SignalComponents will actually arrive. There are some tradeoffs with them, and the question if it is really worth it, given that zoneless-based Change Detection is already quite performant.
The Angular team also wants to close the gap to the overall JavaScript ecosystem and therefore more compatibility with Vite is important. Vite is going to change to Rolldown. So that is a topic for Angular as well but for us developers, the main contact with the build tool is and will always be the Angular CLI.
And for testing: Karma will be replaced with the Modern Web Test runner and there is question if the second supported testing frameworks should be Jest or Vitest. According to Minko one of the important things is that the tests run in the browser. So that speaks more for Vitest.
Another interesting statement was the need for Angular Animations. Minko argued that a lot things in modern browser work already natively and Mark said that an announcement will come quite soon.
Two days later, Matthieu Riegler posted a PR where angular material removes the dependency to angular animations.
Outlook Angular 19.2
The resource function will receive a streaming option, which - extremely simplified - allows a Promise to emit multiple times.
Resource allows us to run an asynchronous task internally, and the value is exposed to the outside via a Signal.
Whereas the resource internally needs to return a Promise, which means it emits a value only one time. rxResource returns internally an Observable, which can emit multiple times.
With stream, you create internally a Signal, which can emit multiple times and pack it into the Promise. To the outside, nothing has changed, we still get our value as a Signal of a type or undefined but internally we are not limited anymore to return just one value.
For more details, you can watch the video clips from TechStacknation, where Alex Rickbaugh, the Angular framework lead, explains it. Or you can also read two article from Manfred Steyer, where he's showing the new possibilities to implement a chat with resource.
Next to that, there are also other upcoming features. For example support for template literals in the template. For a closer look Igor Sedov has you covered with his high-quality animations videos.
Miscellaneous
In other news, Tailwind CSS, a very popular CSS framework, has been released in version. It comes with better performance, makes more use of native features, has a more simpler setup and many other things.
Nx, an alternative to the Angular CLI, has released a series of blogpost and they are working on a new approach how to significantly reduce the amount of the typechecking phase for TypeScript. Quite often, that is a big chunk of the actual build time.
Don't miss the release of the Angular Documentary on 4. Februrary:
Top comments (0)