Angular 19 brings some exciting improvements—Event Replay, zoneless states, and most notably, linkedSignal. Of all the new features, linkedSignal stands out as a clear evolution of Angular’s reactivity model. It’s fast, intuitive, and drastically cuts down boilerplate while boosting performance. To me, it represents peak Angular—powerful, performant, and simple to use.

Most applications leverage API requests to fetch data. Considering data fetching is crucial for Angular testing. Consequently, it's common to include HttpClient in your unit tests.

There is a common misconception among frontend developers that you should not unit test the template of a component. This is incorrect. Not only can you test your components' templates, but you should.

Can two Angular components communicate without the @Output event emitter using only the @Input parameter? Yes, they can, and we will go through the perfect use case of this uncommon approach.

As an Angular developer, you understand the importance of building high-performing web apps. Slow loading times, sluggish UI, and poor user experience can all harm your website's reputation and deter users from returning.

Did you know you can use the catchError RxJS operator to catch errors without unsubscribing? It’s true! It all depends on where you plan to use the operator.

What if your frameworks could work together? Well, with a single-spa Angular application, they can! When you build a single-spa Angular application, painless migration, independent deployment, and effortless scalability are all in store.