You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project rethinks the Angular reactivity model by introducing Signals as a reactivity primitive. Fully implemented, the project will make Zone.js optional. The initial planning resulted in hundreds of discussions, conversations with developers, feedback sessions, user experience studies, and a series of RFCs, which received over 1,000 comments.
45
+
This project rethinks the Angular reactivity model by introducing Signals as a reactivity primitive. The initial planning resulted in hundreds of discussions, conversations with developers, feedback sessions, user experience studies, and a series of RFCs, which received over 1,000 comments.
35
46
36
-
As part of the v17 release, we graduated the Angular Signals library from developer preview. Next we’ll continue implementing the proposals from the RFC. The first steps will be introducing signal-based inputs and queries.
47
+
As part of the v17 release, we graduated the Angular Signals library from developer preview. In v18 you can now use signal-based queries, inputs, and model inputs in developer preview. Next we'll continue addressing community feedback before graduating these APIs to stable and integrate signals deeper in Angular's change detection mechanism.
37
48
</docs-card>
38
-
</docs-card-container>
49
+
<docs-cardtitle="Zoneless Angular"href="">
50
+
In v18 we shipped experimental zoneless support in Angular. It enables developers to use the framework without including zone.js in their bundle, which improves performance, debugging experience, and interoperability. As part of the initial release we also introduced zoneless support to the Angular CDK and Angular Material.
39
51
40
-
### Make Angular easier to learn
41
-
42
-
<docs-card-container>
43
-
<docs-cardtitle="Make Angular.dev the official home for Angular developers"href="https://goo.gle/angular-dot-dev">
44
-
Angular.dev will be the new site, domain and home for Angular development. The new site contains updated documentation, tutorials and guidance that will help developers build with Angular’s latest features. v17’s launch includes new and revised documentation on Angular’s core features, tutorials and reference materials. In the coming months, we will continue to collect feedback and improve the site, with a ton of enhancements planned.
45
-
46
-
In v18, after collecting feedback and continuing to stabilize Angular.dev, we plan to make Angular.dev the official home for all Angular development.
52
+
As the next step, we'll continue iterating on the API to improve developer experience.
47
53
</docs-card>
48
-
<docs-cardtitle="Introduce built-in control flow"href="https://github.com/angular/angular/discussions/50719">
49
-
In v17 we shipped a developer preview version of a new control flow. It brings significant performance improvements and better ergonomics for template authoring. We also provided a migration of existing `*ngIf`, `*ngFor`, and `*ngSwitch` which you can run to move your project to the new implementation. As the next steps we'll be working on addressing community feedback before officially completing this project and graduating it from developer preview.
Local template variables is one of the most upvoted features in the Angular issue tracker. In Q2 2024 we started initial design and prototyping. Expect updates later in 2024.
50
56
</docs-card>
51
57
</docs-card-container>
52
58
53
59
### Improve Angular Material and the CDK
54
60
55
61
<docs-card-container>
56
-
<docs-cardtitle="Expand the customizability of Angular Material"href="">
57
-
To provide better customization of our Angular Material components and enable Material 3 capabilities, we'll be collaborating with Google's Material Design team on defining token-based theming APIs.
58
-
59
-
As of Q4 2023, we're refactoring components to use the new API, finalizing the comprehensive set of tokens, and updating the Sass API based on the new tokens.
60
-
</docs-card>
61
62
<docs-cardtitle="New CDK primitives"href="">
62
63
We are working on new CDK primitives to facilitate creating custom components based on the WAI-ARIA design patterns for [Combobox](https://www.w3.org/TR/wai-aria-practices-1.1/#combobox). Angular v14 introduced stable [menu and dialog primitives](https://material.angular.io/cdk/categories) as part of this project, and in v15 Listbox.
63
64
</docs-card>
@@ -70,13 +71,9 @@ Start developing with the latest Angular features from our roadmap. This list re
70
71
71
72
<docs-card-container>
72
73
<docs-cardtitle="Modernize unit testing tooling with ng test"href="">
73
-
In v12, we revisited the Angular end-to-end testing experience by replacing Protractor with modern alternatives such as Cypress, Nightwatch, and Webdriver.io. Next, we'd like to tackle `ng test` to modernize Angular's unit testing experience. In Q2, we introduced experimental [Jest](https://jestjs.io/) support and [announced](https://blog.angular.io/moving-angular-cli-to-jest-and-web-test-runner-ef85ef69ceca) the transition from Karma to the [Web Test Runner](https://modern-web.dev/docs/test-runner/overview/).
74
-
</docs-card>
75
-
<docs-cardtitle="iframe support in Angular DevTools"href="">
76
-
We are working on making it possible to debug and profile Angular apps embedded within an iframe on the page. This feature will allow you to select an iframe and inspect it directly within Angular DevTools.
77
-
</docs-card>
78
-
<docs-cardtitle="Automation for transition of existing hybrid rendering projects to esbuild and vite"href="tools/cli/esbuild">
79
-
In v17 we shipped a vite and esbuild-based application builder and enabled it for new projects by default. It improves build time for projects using hybrid rendering with up to 87%. Next, we'll be working on developing schematics that migrate existing projects using hybrid rendering to the new build pipeline.
74
+
In v12, we revisited the Angular end-to-end testing experience by replacing Protractor with modern alternatives such as Cypress, Nightwatch, and Webdriver.io. Next, we'd like to tackle `ng test` to modernize Angular's unit testing experience. In Q2 2023, we introduced experimental [Jest](https://jestjs.io/) support and [announced](https://blog.angular.io/moving-angular-cli-to-jest-and-web-test-runner-ef85ef69ceca) the transition from Karma to the [Web Test Runner](https://modern-web.dev/docs/test-runner/overview/).
75
+
76
+
Later this year we'll continue making progress towards introducing Web Test Runner as the replacement of Karma.
80
77
</docs-card>
81
78
<docs-cardtitle="Streamline standalone imports with Language Service"href="">
82
79
As part of this initiative, the language service automatically imports components and pipes in standalone and NgModule-based apps. Additionally, to enable smaller app bundles, we'll work on allowing the language service to propose the automatic removal of unused imports.
@@ -86,11 +83,18 @@ Start developing with the latest Angular features from our roadmap. This list re
86
83
## Fast by default
87
84
88
85
<docs-card-container>
89
-
<docs-cardtitle="Enabling hybrid rendering by default (SSR and SSG)"href="">
90
-
We are working on more developer experience improvements which will allow us to enable hybrid (server-side rendering and static site generation) rendering by default for new projects. In particular, we're focused on route-level rendering strategy configuration and improving developer experience for i18n support.
86
+
<docs-cardtitle="Exploration of partial hydration"href="">
87
+
In v17 we graduated hydration from developer preview and we've been consistently observing 40-50% improvements in LCP. Since then we started prototyping partial hydration and shared a demo on stage at ng-conf. Expect an experimental support in 2024.
88
+
</docs-card>
89
+
<docs-cardtitle="Event replay with SSR and prerendering"href="https://angular.dev/api/platform-browser/withEventReplay">
90
+
In v18 we introduced an event replay functionality when using server-side rendering or prerendering. For this feature we depend on the event dispatch primitive (previously known as jsaction) that is running on Google.com.
91
+
92
+
Over the next couple of months we'll be collecting feedback from the community for this feature and work towards graduating it to stable.
In v17 we shipped deferrable views in developer preview, which provide an ergonomic API for deferred code loading. As the next step we'll be iterating on community feedback before officially making this feature stable.
We're working towards enabling a more ergonomic route configuration on the server. We want to make it trivial to declare which routes should be server-side rendered, prerendered or client-side rendered.
96
+
97
+
As of right now, we're in early design and prototyping phase. Expect updates later in 2024.
94
98
</docs-card>
95
99
</docs-card-container>
96
100
@@ -103,30 +107,50 @@ This section represents explorations and prototyping of potential future project
103
107
With the evolution of Signals in Angular, we'll be also working on a better tooling for debugging them. High on the priority list is a UI for inspecting and debugging Signal-based components.
Angular CLI currently supports HMR via `ng serve --hmr`. Under the hood, this mostly rerenders the Angular application from scratch, which is better than a full page reload, but can definitely be improved. Most importantly, our strategy here should be to optimize the turnaround time for any given change scaled with the frequency of that kind of change. In the future, our team will explore a number of opportunities for improving HMR, including:
110
+
Angular CLI currently supports HMR via `ng serve --hmr`. Under the hood, this mostly rerenders the Angular application from scratch, which is better than a full page reload, but can definitely be improved. Most importantly, our strategy here should be to optimize the turnaround time for any given change scaled with the frequency of that kind of change. In the future, our team will explore a number of opportunities for improving HMR, including:
107
111
108
112
- Fast track CSS-only changes and apply them to any existing components on the page.
109
113
- Fast track Angular template-only changes and apply them to any existing components on the page.
110
114
</docs-card>
111
115
<docs-cardtitle="Exploration of streamed server-side rendering"href="">
112
116
Over the past few releases we've been working on making Angular's server-side rendering story more robust. On our priority list is to explore streamed server-side rendering for zoneless application.
113
117
</docs-card>
114
-
<docs-cardtitle="Exploration of partial hydration"href="">
115
-
In v17 we graduated hydration from developer preview and we've been consistently observing 40-50% improvements in LCP. As the next step, we'll explore how we can partially hydrate applications using deferrable views.
116
-
117
-
As part of this effort, we'll be also evaluating the trade-offs of more fine-grained hydration and resumability. We'll share updates as we progress.
118
-
</docs-card>
119
118
<docs-cardtitle="Investigation for authoring format improvements"href="">
120
119
Based on our developer surveys' results we saw there are opportunities for improving the ergonomics of the component authoring format. The first step of the process will be to gather requirements and understand the problem space in advanced to an RFC. We'll share updates as we make progress. High priority in the future work will be backward compatibility and interoperability.
As part of this project, we'd like to implement mixed orientation support for the Angular CDK drag and drop. This is one of the repository's most highly requested features.
124
123
</docs-card>
124
+
<docs-cardtitle="Evaluating Nitro support in the Angular CLI"href="https://nitro.unjs.io/">
125
+
We're excited about the set of features that Nitro offers such as portability, minimal design, and file-based routing. Later this year we'll evaluate how it fits in the Angular server-side rendering model.
126
+
127
+
We'll share updates as we make progress in this investigation.
128
+
</docs-card>
125
129
</docs-card-container>
126
130
127
131
## Completed projects
128
132
129
133
<docs-card-container>
134
+
<docs-cardtitle="Expand the customizability of Angular Material"link="Completed in Q2 2024"href="https://material.angular.io/guide/theming">
135
+
To provide better customization of our Angular Material components and enable Material 3 capabilities, we'll be collaborating with Google's Material Design team on defining token-based theming APIs.
136
+
137
+
In v17.2 we shared experimental support for Angular Material 3 and in v18 we graduated it to stable.
138
+
</docs-card>
139
+
<docs-cardtitle="Introduce deferred loading"link="Completed in Q2 2024"href="https://next.angular.dev/guide/defer">
140
+
In v17 we shipped deferrable views in developer preview, which provide an ergonomic API for deferred code loading. In v18 we enabled deferrable views for library developers and graduated the API to stable.
141
+
</docs-card>
142
+
<docs-cardtitle="iframe support in Angular DevTools"link="Completed in Q2 2024"href="">
143
+
We enabled debugging and profiling of Angular apps embedded within an iframe on the page.
144
+
</docs-card>
145
+
<docs-cardtitle="Automation for transition of existing hybrid rendering projects to esbuild and vite"link="Completed in Q2 2024"href="tools/cli/esbuild">
146
+
In v17 we shipped a vite and esbuild-based application builder and enabled it for new projects by default. It improves build time for projects using hybrid rendering with up to 87%. As part of v18 we shipped schematics and a guide that migrate existing projects using hybrid rendering to the new build pipeline.
147
+
</docs-card>
148
+
<docs-cardtitle="Make Angular.dev the official home for Angular developers"link="Completed in Q2 2024"href="https://goo.gle/angular-dot-dev">
149
+
Angular.dev is the new site, domain and home for Angular development. The new site contains updated documentation, tutorials and guidance that will help developers build with Angular’s latest features.
150
+
</docs-card>
151
+
<docs-cardtitle="Introduce built-in control flow"link="Completed in Q2 2024"href="https://next.angular.dev/essentials/conditionals-and-loops">
152
+
In v17 we shipped a developer preview version of a new control flow. It brings significant performance improvements and better ergonomics for template authoring. We also provided a migration of existing `*ngIf`, `*ngFor`, and `*ngSwitch` which you can run to move your project to the new implementation. As of v18 the built-in control flow is now stable.
153
+
</docs-card>
130
154
<docs-cardtitle="Modernize getting started tutorial"link="Completed Q4 2023"href="">
131
155
Over the past two quarters, we developed a new [video](https://www.youtube.com/watch?v=xAT0lHYhHMY&list=PL1w1q3fL4pmj9k1FrJ3Pe91EPub2_h4jF) and [textual](https://angular.dev/tutorials/learn-angular) tutorial based on standalone components.
0 commit comments