Title: Roadmap • Angular
Open Graph Title: Roadmap • Angular
X Title: Roadmap • Angular
Description: The web development framework for building modern apps.
Open Graph Description: The web development framework for building modern apps.
X Description: The web development framework for building modern apps.
Keywords:
Opengraph URL: https://angular.dev/
X: @Angular
Domain: angular.dev
| author | Angular Team |
| apple-mobile-web-app-title | Angular |
| application-name | Angular |
| msapplication-TileColor | #e90464 |
| msapplication-config | /assets/icons/browserconfig.xml |
| theme-color | #ffffff |
| og:type | website |
| og:image | https://angular.dev/assets/images/ng-image.jpg |
| twitter:creator | @Angular |
| twitter:card | summary_large_image |
| twitter:url | https://angular.dev/ |
| twitter:image | https://angular.dev/assets/images/ng-image.jpg |
Links:
| https://angular.dev/ | |
| Docs | https://angular.dev/docs |
| Tutorials | https://angular.dev/tutorials |
| Playground | https://angular.dev/playground |
| Reference | https://angular.dev/reference |
| Roadmap | https://angular.dev/roadmap |
| Get involved | https://github.com/angular/angular/blob/main/CONTRIBUTING.md |
| Versioning and releases | https://angular.dev/reference/releases |
| Version compatibility | https://angular.dev/reference/versions |
| Update guide | https://angular.dev/update-guide |
| Asynchronous reactivity To enable developers to handle asynchronous data flow with signals we developed the resource async primitive. Building on top of it, we introduced httpResource which allows you to send HTTP requests and receive your response as a signal. We're still actively collecting feedback for these new experimental APIs. Please give them a try and share your feedback with us on GitHub! Learn more | https://github.com/angular/angular/discussions/60121 |
| Google Fonts | https://fonts.google.com/ |
| Improve HMR (Hot Module Reload) We're working towards faster edit/refresh cycle by enabling hot module replacement. In Angular v19 we shipped initial support for CSS and template HMR and in v20 we graduated template HMR to stable. We'll continue collecting feedback to make sure we're addressing developers' needs before we mark this project as complete. Learn more | https://github.com/angular/angular/issues/39367#issuecomment-1439537306 |
| Combobox | https://www.w3.org/TR/wai-aria-practices-1.1/#combobox |
| menu and dialog primitives | https://material.angular.dev/cdk/categories |
| Evaluating Nitro support in the Angular CLI We're excited about the set of features that Nitro offers such as more deployment options, improved compatibility of server-side rendering with different runtimes and file-based routing. In 2025 we'll evaluate how it fits in the Angular server-side rendering model. We'll share updates as we make progress in this investigation. Learn more | https://nitro.unjs.io/ |
| Deliver Angular Signals 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. In Angular v20 we graduated all the fundamental reactivity primitives to stable including signal, effect, linkedSignal, signal-based queries, and inputs. Completed in Q2 2025 | https://github.com/angular/angular/discussions/49685 |
| Support two-dimensional drag-and-drop As part of this project, we implemented mixed orientation support for the Angular CDK drag and drop. This is one of the repository's most highly requested features. Completed in Q2 2024 | https://github.com/angular/components/issues/13372 |
| Event replay with SSR and prerendering 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. In Angular v19 we graduated event replay to stable and enabled it by default for all new projects. Completed in Q4 2024 | https://angular.dev/api/platform-browser/withEventReplay |
| @let docs | https://angular.dev/api/core/@let |
| Expand the customizability of Angular Material 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. In v17.2 we shared experimental support for Angular Material 3 and in v18 we graduated it to stable. Completed in Q2 2024 | https://material.angular.dev/guide/theming |
| Introduce deferred loading 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. Completed in Q2 2024 | https://next.angular.dev/guide/defer |
| Automation for transition of existing hybrid rendering projects to esbuild and vite 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. Completed in Q2 2024 | https://angular.dev/tools/cli/build-system-migration |
| Make Angular.dev the official home for Angular developers 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. Completed in Q2 2024 | https://goo.gle/angular-dot-dev |
| Introduce built-in control flow 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. Completed in Q2 2024 | https://next.angular.dev/essentials/conditionals-and-loops |
| video | https://www.youtube.com/watch?v=xAT0lHYhHMY&list=PL1w1q3fL4pmj9k1FrJ3Pe91EPub2_h4jF |
| textual | https://angular.dev/tutorials/learn-angular |
| Investigate modern bundlers In Angular v16, we released a developer preview of an esbuild-based builder with support for ng build and ng serve. The ng serve development server uses Vite and a multi-file compilation by esbuild and the Angular compiler. In v17 we graduated the build tooling from developer preview and enabled it by default for new projects. Completed Q4 2023 | https://angular.dev/guide/hydration |
| Introduce dependency injection debugging APIs To improve the debugging utilities of Angular and Angular DevTools, we'll work on APIs that provide access to the dependency injection runtime. As part of the project, we'll expose debugging methods that allow us to explore the injector hierarchy and the dependencies across their associated providers. As of v17, we shipped a feature that enables us to plug into the dependency injection life-cycle. We also launched a visualization of the injector tree and inspection of the providers declared inside each individual node, Completed Q4 2023 | https://angular.dev/tools/devtools |
| Improve documentation and schematics for standalone components We released a developer preview of the ng new --standalone schematics collection, allowing you to create apps free of NgModules. In v17 we switched the new application authoring format to standalone APIs and changed the documentation to reflect the recommendation. Additionally, we shipped schematics which support updating existing applications to standalone components, directives, and pipes. Even though NgModules will stick around for foreseeable future, we recommend you to explore the benefits of the new APIs to improve developer experience and benefit from the new features we build for them. Completed Q4 2023 | https://angular.dev/components |
| hydration guide | https://angular.dev/guide/hydration |
| blog post | https://blog.angular.dev/whats-next-for-server-side-rendering-in-angular-2a6f27662b67 |
| LCP | https://web.dev/lcp |
| CLS | https://web.dev/cls |
| Non-destructive full app hydration In v16, we released a developer preview of non-destructive full hydration, which allows Angular to reuse existing DOM nodes on a server-side rendered page, instead of re-creating an app from scratch. See additional information in the hydration guide. Completed Q1 2023 | https://angular.dev/guide/hydration |
| Improvements in the image directive We released the Angular image directive as stable in v15. We introduced a new fill mode feature that enables images to fit within their parent container rather than having explicit dimensions. Over the past two months, the Chrome Aurora team backported the directive to v12 and newer. Completed Q1 2023 | https://angular.dev/guide/image-optimization |
| Documentation refactoring Ensure all existing documentation fits into a consistent set of content types. Update excessive use of tutorial-style documentation into independent topics. We want to ensure the content outside the main tutorials is self-sufficient without being tightly coupled to a series of guides. In Q2 2022, we refactored the template content and dependency injection. In Q1 2023, we improved the HTTP guides, and with this, we're putting the documentation refactoring project on hold. Completed Q1 2023 | https://angular.io |
| Improve image performance The Aurora and the Angular teams are working on the implementation of an image directive that aims to improve Core Web Vitals. We shipped a stable version of the image directive in v15. Completed Q4 2022 | https://angular.dev/guide/image-optimization |
| Modern CSS The Web ecosystem evolves constantly and we want to reflect the latest modern standards in Angular. In this project we aim to provide guidelines on using modern CSS features in Angular to ensure developers follow best practices for layout, styling, etc. We shared official guidelines for layout and as part of the initiative stopped publishing flex layout. Completed Q4 2022 | https://blog.angular.dev/modern-css-in-angular-layouts-4a259dca9127 |
| Support adding directives to host elements A long-standing feature request is to add the ability to add directives to host elements. The feature lets developers augment their own components with additional behaviors without using inheritance. In v15 we shipped our directive composition API, which enables enhancing host elements with directives. Completed Q4 2022 | https://angular.dev/guide/directives/directive-composition-api |
| Better stack traces The Angular and the Chrome DevTools are working together to enable more readable stack traces for error messages. In v15 we released improved relevant and linked stack traces. As a lower priority initiative, we'll be exploring how to make the stack traces friendlier by providing more accurate call frame names for templates. Completed Q4 2022 | https://developer.chrome.com/blog/devtools-better-angular-debugging/ |
| Enhanced Angular Material components by integrating MDC Web MDC Web is a library created by the Google Material Design team that provides reusable primitives for building Material Design components. The Angular team is incorporating these primitives into Angular Material. Using MDC Web aligns Angular Material more closely with the Material Design specification, expands accessibility, improves component quality, and improves the velocity of our team. Completed Q4 2022 | https://material.angular.dev/guide/mdc-migration |
| Implement APIs for optional NgModules In the process of making Angular simpler, we are working on introducing APIs that allow developers to initialize apps, instantiate components, and use the router without NgModules. Angular v14 introduces developer preview of the APIs for standalone components, directives, and pipes. In the next few quarters we'll collect feedback from developers and finalize the project making the APIs stable. As the next step we will work on improving use cases such as TestBed, Angular elements, etc. Completed Q4 2022 | https://blog.angular.dev/angular-v15-is-now-available-df7be7f2f4c8 |
| Allow binding to protected fields in templates To improve the encapsulation of Angular components we enabled binding to protected members of the component instance. This way you'll no longer have to expose a field or a method as public to use it inside your templates. Completed Q2 2022 | https://angular.dev/guide/templates/binding |
| Publish guides on advanced concepts Develop and publish an in-depth guide on change detection. Develop content for performance profiling of Angular apps. Cover how change detection interacts with Zone.js and explain when it gets triggered, how to profile its duration, as well as common practices for performance optimization. Completed Q2 2022 | https://angular.io/guide/change-detection |
| Rollout strict typings for @angular/forms In Q4 2021 we designed a solution for introducing strict typings for forms and in Q1 2022 we concluded the corresponding request for comments. Currently, we are implementing a rollout strategy with an automated migration step that will enable the improvements for existing projects. We are first testing the solution with more than 2,500 projects at Google to ensure a smooth migration path for the external community. Completed Q2 2022 | https://angular.dev/guide/forms/typed-forms |
| Remove legacy View Engine After the transition of all our internal tooling to Ivy is completed, we will remove the legacy View Engine for reduced Angular conceptual overhead, smaller package size, lower maintenance cost, and lower codebase complexity. Completed Q1 2022 | https://blog.angular.dev/angular-v15-is-now-available-df7be7f2f4c8 |
| Simplified Angular mental model with optional NgModules To simplify the Angular mental model and learning journey, we will be working on making NgModules optional. This work lets developers develop standalone components and implement an alternative API for declaring the compilation scope of the component. We kicked this project off with high-level design discussions that we captured in an RFC. Completed Q1 2022 | https://blog.angular.dev/angular-v15-is-now-available-df7be7f2f4c8 |
| Design strict typing for @angular/forms We will work on finding a way to implement stricter type checking for reactive forms with minimal backward incompatible implications. This way, we let developers catch more issues during development time, enable better text editor and IDE support, and improve the type checking for reactive forms. Completed Q1 2022 | https://angular.dev/guide/forms/typed-forms |
| Improve integration of Angular DevTools with framework To improve the integration of Angular DevTools with the framework, we are working on moving the codebase to the angular/angular monorepository. This includes transitioning Angular DevTools to Bazel and integrating it into the existing processes and CI pipeline. Completed Q1 2022 | https://angular.dev/tools/devtools |
| Launch advanced compiler diagnostics Extend the diagnostics of the Angular compiler outside type checking. Introduce other correctness and conformance checks to further guarantee correctness and best practices. Completed Q1 2022 | https://angular.dev/reference/extended-diagnostics |
| Update our e2e testing strategy To ensure we provide a future-proof e2e testing strategy, we want to evaluate the state of Protractor, community innovations, e2e best practices, and explore novel opportunities. As first steps of the effort, we shared an RFC and worked with partners to ensure smooth integration between the Angular CLI and state-of-the-art tooling for e2e testing. As the next step, we need to finalize the recommendations and compile a list of resources for the transition. Completed Q3 2021 | https://angular.dev/guide/testing |
| Angular libraries use Ivy Earlier in 2020, we shared an RFC for Ivy library distribution. After invaluable feedback from the community, we developed a design of the project. We are now investing in the development of Ivy library distribution, including an update of the library package format to use Ivy compilation, unblock the deprecation of the View Engine library format, and ngcc. Completed Q3 2021 | https://angular.dev/tools/libraries |
| Improve test times and debugging with automatic test environment tear down To improve test time and create better isolation across tests, we want to change TestBed to automatically clean up and tear down the test environment after each test run. Completed Q3 2021 | https://angular.dev/guide/testing |
| Deprecate and remove IE11 support Internet Explorer 11 (IE11) has been preventing Angular from taking advantage of some of the modern features of the Web platform. As part of this project we are going to deprecate and remove IE11 support to open the path for modern features that evergreen browsers provide. We ran an RFC to collect feedback from the community and decide on next steps to move forward. Completed Q3 2021 | https://github.com/angular/angular/issues/41840 |
| Leverage ES2017+ as the default output language Supporting modern browsers lets us take advantage of the more compact, expressive, and performant new syntax of JavaScript. As part of this project we will investigate what the blockers are to moving forward with this effort, and take the steps to enable it. Completed Q3 2021 | https://www.typescriptlang.org/docs/handbook/tsconfig-json.html |
| Accelerated debugging and performance profiling with Angular DevTools We are working on development tooling for Angular that provides utilities for debugging and performance profiling. This project aims to help developers understand the component structure and the change detection in an Angular app. Completed Q2 2021 | https://angular.dev/tools/devtools |
| Streamline releases with consolidated Angular versioning & branching We want to consolidate release management tooling between the multiple GitHub repositories for Angular (angular/angular, angular/angular-cli, and angular/components). This effort lets us reuse infrastructure, unify and simplify processes, and improve the reliability of our release process. Completed Q2 2021 | https://angular.dev/reference/releases |
| Higher developer consistency with commit message standardization We want to unify commit message requirements and conformance across Angular repositories (angular/angular, angular/components, and angular/angular-cli) to bring consistency to our development process and reuse infrastructure tooling. Completed Q2 2021 | https://github.com/angular/angular |
| Transition the Angular language service to Ivy The goal of this project is to improve the experience and remove legacy dependency by transitioning the language service to Ivy. Today the language service still uses the View Engine compiler and type checking, even for Ivy apps. We want to use the Ivy template parser and improved type checking for the Angular Language service to match app behavior. This migration is also a step towards unblocking the removal of View Engine, which will simplify Angular, reduce the npm package size, and improve the maintainability of the framework. Completed Q2 2021 | https://angular.dev/tools/language-service |
| Increased security with native Trusted Types in Angular In collaboration with the Google security team, we are adding support for the new Trusted Types API. This web platform API helps developers build more secure web apps. Completed Q2 2021 | https://angular.dev/best-practices/security |
| Optimized build speed and bundle sizes with Angular CLI webpack 5 As part of the v11 release, we introduced an opt-in preview of webpack 5 in the Angular CLI. To ensure stability, we will continue iterating on the implementation to enable build speed and bundle size improvements. Completed Q2 2021 | https://angular.dev/tools/cli/build |
| Faster apps by inlining critical styles in Universal apps Loading external stylesheets is a blocking operation, which means that the browser cannot start rendering your app until it loads all the referenced CSS. Having render-blocking resources in the header of a page can significantly impact its load performance, for example, its first contentful paint. To make apps faster, we have been collaborating with the Google Chrome team on inlining critical CSS and loading the rest of the styles asynchronously. Completed Q1 2021 | https://angular.dev/guide/ssr |
| Improve debugging with better Angular error messages Error messages often bring limited actionable information to help developers resolve them. We have been working on making error messages more discoverable by adding associated codes, developing guides, and other materials to ensure a smoother debugging experience. Completed Q1 2021 | https://angular.dev/reference/errors |
| Improved developer onboarding with refreshed introductory documentation We will redefine the user learning journeys and refresh the introductory documentation. We will clearly state the benefits of Angular, how to explore its capabilities and provide guidance so developers can become proficient with the framework in as little time as possible. Completed Q1 2021 | https://angular.dev/tutorials |
| Expand component harnesses best practices Angular CDK introduced the concept of component test harnesses to Angular in version 9. Test harnesses let component authors create supported APIs for testing component interactions. We are continuing to improve this harness infrastructure and clarifying the best practices around using harnesses. We are also working to drive more harness adoption inside of Google. Completed Q1 2021 | https://material.angular.dev/guide/using-component-harnesses |
| Author a guide for content projection Content projection is a core Angular concept that does not have the presence it deserves in the documentation. As part of this project we want to identify the core use cases and concepts for content projection and document them. Completed Q2 2021 | https://angular.io/docs |
| Migrate to ESLint With the deprecation of TSLint we will be moving to ESLint. As part of the process, we will work on ensuring backward compatibility with our current recommended TSLint configuration, implement a migration strategy for existing Angular apps and introduce new tooling to the Angular CLI toolchain. Completed Q4 2020 | https://angular.dev/tools/cli |
| Operation Bye Bye Backlog (also known as Operation Byelog) We are actively investing up to 50% of our engineering capacity on triaging issues and PRs until we have a clear understanding of broader community needs. After that, we will commit up to 20% of our engineering capacity to keep up with new submissions promptly. Completed Q4 2020 | https://github.com/angular/angular/issues |
| Blog | https://blog.angular.dev |
| X (formerly Twitter) | https://x.com/angular |
| Bluesky | https://bsky.app/profile/angular.dev |
| YouTube | https://www.youtube.com/angular |
| Discord | https://discord.gg/angular |
| GitHub | https://github.com/angular/angular |
| Stack Overflow | https://stackoverflow.com/questions/tagged/angular |
| Contribute | https://github.com/angular/angular/blob/main/CONTRIBUTING.md |
| Code of Conduct | https://github.com/angular/code-of-conduct/blob/main/CODE_OF_CONDUCT.md |
| Report Issues | https://github.com/angular/angular/issues |
| Google's DevLibrary | https://devlibrary.withgoogle.com/products/angular?sort=updated |
| Angular Google Developer Experts | https://developers.google.com/community/experts/directory?specialization=angular |
| Press Kit | https://angular.dev/press-kit |
| Roadmap | https://angular.dev/roadmap |
| 简体中文版 | https://angular.cn/ |
| 正體中文版 | https://dev.angular.tw/ |
| 日本語版 | https://angular.jp/ |
| 한국어 | https://angular.kr/ |
| MIT-style License | https://angular.dev/license |
| CC BY 4.0 | https://creativecommons.org/licenses/by/4.0/ |
Viewport: width=device-width, initial-scale=1