Learn Angular 19: Enhance Your Developer Skills Today
Description
Explore effective ways to learn Angular 19 and improve your developer experience with the latest v19 enhancements.
In the past two years we doubled down on our investment in developer experience and performance — in every single release we’ve been consistently shipping improvements that multiply their impact when combined together. Seeing the positive community response and increased engagement in our developer events is validating that we’ve been moving in the right direction. Today’s release is bringing a series of improvements that will make it even easier for you to deliver fast web apps with confidence.
A few highlights:
- Developer preview of incremental hydration supporting the most performance demanding use cases
- Schematics to keep you up to date with the latest best practices — inputs, outputs, queries, inject-based dependency injection, and new build system
- Stabilization of core reactivity primitives and introduction of new ones:
linkedSignalandresource - Series of quality of life improvements addressing feature requests with more than 2,700 đź‘Ť on GitHub! This includes time picker component, unused import removal, running schematics via the language service, HMR for styles, and more!
You can watch a quick overview of the release from our special event video. For a more holistic list of the features and improvements in v19, continue reading below.
Build for speed
Evolving Angular we see the opportunity to enable best performance practices out of the box, so that we can support your performance-sensitive use cases. In the past two years we kicked off a project to enable zoneless Angular, made server-side rendering an integral part of the Angular CLI, and worked closely with Chrome Aurora on hydration and the image directive.
In version 19, we’re elevating Angular server-side rendering to another level with incremental hydration, server route configuration, event replay enabled by default, and more.
Building large web apps increases the amount of JavaScript we ship to the user, which negatively impacts user experience. In v17 we made it trivial to lazily load code with deferrable views for client-side rendered apps. For server-side rendered applications we introduced full-app hydration which requires all the JavaScript associated with a given page to make it interactive. Today, we’re delivering a solution to the server that is inspired by deferrable views!
Instant angular 19 edit/refresh with hot module replacement
Prior to this improvement, every time you change the style or template of a component and save the file, Angular CLI would rebuild your app and send a notification to the browser which would refresh.
Our new HMR will compile the style or template you modified, send the result to the browser, and patch your app without a page refresh and any state loss. That way you’ll have a faster turnaround cycle and uninterrupted flow state.
Standalone defaults to true
We introduced standalone components over two years ago in v14. In the last developer survey over 90% of developers said they are using this feature. As part of v19 we are providing a schematic that will run as part of ng update and will automatically remove the standalone component metadata property for all your standalone directives, components, and pipes and set standalone to false for all non-standalone abstractions.
For more information, check our update guide on update.angular.dev. Thanks Matthieu Riegler for this contribution!
Evolving reactivity
A core theme for Angular over the past two years has been evolving our reactivity system. In version 19, we’re excited to share a couple of new complimentary APIs and the stabilization of some of the fundamental reactivity APIs we introduced in previous versions, such as input, output, and view queries.
Modernize your code via the language service
A core theme for Angular over the past two years has been evolving our reactivity system. In version 19, we’re excited to share a couple of new complimentary APIs and the stabilization of some of the fundamental reactivity APIs we introduced in previous versions, such as input, output, and view queries.