Category: Angular

In the 3-2-1 format of the newsletter, I’m posting a few essential articles to revisit, updates to know about, and one question to ponder:

Three (or four) Angular updates to know about:

• The Angular team started teasing its new “selector-less” RFC with some examples of what this could look like. The goal is to get rid of component and directive selectors (and hopefully extra imports) and this could be available as an experiment as soon as Angular v20:
  

• We now have a date and location for ng-conf 2025: October 17-18 in Baltimore, USA. The event is moving closer to Europe and will be preceded by JSConf North America at the same venue on October 14-16.
• All videos from FrontEnd Nation Angular Day are now available on this Youtube playlist.
• You can already register for free for the next FrontendNation Event (3-5 June) at https://frontendnation.com/

Two articles to revisit:

• None this week, lots of videos to watch in the previous section!

One little thing to ponder:

• Did you know that instead of using [class]=" isImportant ? 'highlight' : ' ' " you can do [class.highlight] ="isImportant" in your templates?

This week, we’re back to using the 3-2-1 format of the newsletter. I’m posting a few essential articles to revisit, updates to know about, and one question to ponder:

Three short articles to revisit:

• Do you know there are several types of RxJs subjects? And when to use each kind? I cover 3 of them in this article.
• This tutorial is about a 4th type of Subject: WebSocketSubject for web socket connections.
• Finally, a trick to emit Observable data directly into a Subject.

Two Angular updates:

• ng-conf will be back this fall in the US! That is great news. On top of that, Angular Connect will be back in London, UK on September 13th 2025. Tickets are already available!

• Next week on March 27th, we’ll be running Frontend Nation Angular Day with Minko Gechev, Sarah Drasner, and more GDEs and Angular team members! It’s a free, online event. Save the date now and register here.

One question to think about:

• Did you know that the Angular dev tools display current Signal values? Makes it super easy to debug Angular code without breakpoints!

This week, we’re back to using the 3-2-1 format of the newsletter. I’m posting a few essential articles to revisit, updates to know about, and one question to ponder:

Three short articles to revisit:

• You probably know about lazy-loading, but have you considered using the @defer block with its prefetching and different trigger options? These features give you a lot more control over lazy-loading and don’t rely on routing at all.

Two Angular updates:

• Angular 19.2 is available! It comes with quite a few interesting experimental features, such as a new httpResource (the signal-based alternative to HttpClient), a defaultValue option for resources, the ability to use JavaScript template strings in Angular templates, as well a new CLI migration to use self-closing tags: ⁠ng generate @angular/core:self-closing-tag

• On March 27th, we’ll be running Frontend Nation Angular Day with Minko Gechev, Sarah Drasner, and Jessica Janiuk from the Angular team! It’s a free, online event. Save the date now and register here.
  
  

One question to think about:

• Have you tried the resource API? It’s promising, and the Angular team is considering it as the solution for reactivity with Signals and without RxJs. Check out my quick tutorial here.

As usual, we’re using the 3-2-1 format of the newsletter this week. I’m posting a few essential articles to revisit, updates to know about, and one question to ponder:

Three articles to revisit:

• CSS animations can be tricky as the language constantly evolves with new features and new ways to do what could be done before with various CSS tricks and/or JavaScript. Here is a tool that helps you discover and configure CSS animations for your app, while this tutorial showcases how to animate route transitions with Angular.
• Finally, I wanted to remind you that this Angular template syntax trick can replace ngClass in most scenarios.

Two Angular updates:

• Angular 19.2 just got its first RC version, and it features a new httpResource, which aims to replace the HttpClient with a Signal-based approach. Manfred Steyer published a preview of the feature here.
• The FREE Angular Weekend is happening this weekend at certificates.dev! A great way to get free certification training and take practice tests to see how you’d fare in the Angular mid-level certification exam.

One question to think about:

• Do you still use jQuery or lodash with Angular? Most features of these libraries are now either natively supported (such as object copy) or have Angular alternatives, such as queries and template reference variables.

As usual, we’re using the 3-2-1 format of the newsletter this week. I’m posting a few essential articles to revisit, updates to know about, and one question to ponder:

Three articles to revisit:

• Content projection is an essential and easy technique to create reusable components. For more complex scenarios, you can also use multi-slot content projection, and if you want a full conference workshop recording on that topic, we have that video from ng-conf 2022.

Two Angular updates:

• The Angular team announced its priorities for 2025: Signal forms, RFC for selectorless components (meaning no more imports needed for components !), promote zoneless to developer preview, and replace Karma for unit testing.
• Our FREE monthly online workshop is scheduled for this Thursday, don’t forget to register now. I’ll talk about different simple strategies to migrate from RxJs to Signals in Angular.

One question to think about:

• Signals are stable, with the exception of the effect function. Since Angular is going all in on Signals, with Signal forms being next in the pipeline, have you started migrating your apps to use Signals instead of RxJs? Attend our next free workshop to see me do it live.

This week, we’re using the 3-2-1 format of the newsletter once more. I’m posting a few essential articles to revisit, updates to know about, and one question to ponder:

Three short articles to revisit:

• HTTP interceptors can be used in several ways to assist with authentication, refactoring code, caching data, and more! Read more about them with this tutorial.
• Just like guards and resolvers, HTTP interceptors can also be declared as functions.

Two Angular updates:

• Angular 19.1 is now available! The most interesting addition is a new CLI command to automatically clean-up unused imports: ng g @angular/core:cleanup-unused-imports
• Another interesting update is the support for Typescript 5.7 added to Angular 19.1. More info about Typescript 5.7 here.

One question to think about:

• Do you call methods in your Angular component templates sometimes? If so, check this out to consider a better alternative.

Happy New Year! Let’s get back to the 3-2-1 format of the newsletter. I’m posting a few essential articles to revisit, updates to know about, and one question to ponder – all good knowledge to kickstart 2025 the right way:

Three short articles to revisit:

• Change detection is a tricky topic that keeps evolving as Angular gets better. To get the right mental model of how it works, you can check these posts on change detection illustrated, what markForCheck() is and does, and finally tie this all together by understanding how the async pipe and Signals trigger change detection automatically for us.

Two Angular updates/announcements:

• Angular v20 will be released during the week of May 19th 2025.
• My next FREE online workshop is scheduled for January 23rd, and you can register here. I’ll cover techniques and best practices to migrate to Angular Signals:
  

One question to think about:

Did you know that you don’t always need pipes to format dates or numbers? You can use the functions used by the Angular pipes directly in TypeScript instead.

Angular 19 is a massive release with lots of improvements and new features. I covered all signal-related updates earlier. Today, let’s focus on what’s changed with standalone features in the framework.

First, standalone is the new default! In Angular 19, you don’t need the standalone: true option in your decorators, that’s the default value now. Instead, you want to use standalone: false for features that are not standalone and belong to a ngModule.

When you upgrade to Angular 19, ng update will automatically remove standalone : true where you use it and use standalone: false where needed. No need to worry about it!

Second, the Angular compiler will warn you when you have unused imports in your standalone components. This is great to help keep your code clean:

TS-998113: Imports array contains unused imports [plugin angular-compiler]

src/app/user/users.component.ts:9:27:
9 │ imports: [UserComponent, UnusedComponent],Code language: HTTP (http)

Finally, if you want to make sure all your components are standalone, you can use the new "strictStandalone": true option in the angularCompilerOptions.

Then, if your create a non-standalone feature, you’ll get an error:
TS-992023: Only standalone components/directives are allowed when 'strictStandalone' is enabled.