Ng-News 25/13: resource() RFC Wrap-Up & Frontend Nation Panel

The Frontend Nation panel with Angular team members focused on testing, confirming that Web Test Runner will replace Karma and that the team is still deciding between Jest and Vitest. Meanwhile, the resource RFCs have concluded, with upcoming API changes like renaming request to params and replacing the ResourceStatus enum with a union type. Frontend Nation Panel Frontend Nation did an Angular Day with different talks but also had a panel which included next to Alain Chautard also members of the Angular team, Jeremy Elbourn, Jessica Janinuk, and Sarah Drasner, who is not part of the Angular team is but part of the leadership above it. Surprisingly, one of the main topics was testing. Jeremy confirmed that the Web Test Runner will replace Karma. The team still has to decide between Jest and Vitest. That decision is expected soon, but it’s unclear whether it will already land in Angular v20. Another noteworthy moment came from Sarah Drasner, who addressed the misconception that Google doesn’t use Angular internally. On the contrary, Angular is their most-used framework. frontendnation.com resource() RFC Wrap-Up Meanwhile, the two RFCs for resource functions have been closed, with final remarks from their authors Alex Rickabaugh and Pawel Koszlowski. resource functions are built to derive Signals from asynchronous tasks. We now have resources as the basic function or low-level, rxResource with support for RxJS and httpResource, which fires HTTP requests reactively. As an outcome of the RFC, some changes to the API are already underway, and more are expected. The request property might be renamed to params, and ResourceStatus will become a union type. Especially for the httpResource, there is a demand for supporting mutation, so we also want to change data. That is a topic for the future. The resource functions will keep their experimental status for version 20. Compared to now, I don’t expect version 20 to bring such major changes again. https://github.com/angular/angular/discussions/60120#discussioncomment-12654042 https://github.com/angular/angular/discussions/60121#discussioncomment-12654043 Further Content In other news, Connie Leung started an article series about al the upcoming changes in Angular 20. Dynamically-created components support two-way bindings Connie Leung ・ Mar 24 #anguar #webdev #tutorial Vyacheslav Borodin has written a solid and fairly advanced article on directives in general. Directives: a core feature of the Angular toolkit | by Vyacheslav Borodin | CORETEQ Technology | Mar, 2025 | Medium Vyacheslav Borodin ・ Mar 27, 2025 ・ Medium

Mar 31, 2025 - 20:34

The Frontend Nation panel with Angular team members focused on testing, confirming that Web Test Runner will replace Karma and that the team is still deciding between Jest and Vitest. Meanwhile, the resource RFCs have concluded, with upcoming API changes like renaming request to params and replacing the ResourceStatus enum with a union type.

Frontend Nation Panel

Frontend Nation did an Angular Day with different talks but also had a panel which included next to Alain Chautard also members of the Angular team, Jeremy Elbourn, Jessica Janinuk, and Sarah Drasner, who is not part of the Angular team is but part of the leadership above it.

Surprisingly, one of the main topics was testing. Jeremy confirmed that the Web Test Runner will replace Karma. The team still has to decide between Jest and Vitest. That decision is expected soon, but it’s unclear whether it will already land in Angular v20.

Another noteworthy moment came from Sarah Drasner, who addressed the misconception that Google doesn’t use Angular internally. On the contrary, Angular is their most-used framework.

frontendnation.com

`resource()` RFC Wrap-Up

Meanwhile, the two RFCs for resource functions have been closed, with final remarks from their authors Alex Rickabaugh and Pawel Koszlowski. resource functions are built to derive Signals from asynchronous tasks. We now have resources as the basic function or low-level, rxResource with support for RxJS and httpResource, which fires HTTP requests reactively.
As an outcome of the RFC, some changes to the API are already underway, and more are expected.

The request property might be renamed to params, and ResourceStatus will become a union type.

Especially for the httpResource, there is a demand for supporting mutation, so we also want to change data. That is a topic for the future. The resource functions will keep their experimental status for version 20.
Compared to now, I don’t expect version 20 to bring such major changes again.

https://github.com/angular/angular/discussions/60120#discussioncomment-12654042

https://github.com/angular/angular/discussions/60121#discussioncomment-12654043