Angular 路线图link

Angular Roadmaplink

Angular 从 Google 内部和更广泛的开源社区都收到了大量的特性请求。与此同时，我们的项目列表包含大量维护任务、代码重构、潜在的性能提升等等。我们汇集了来自来自开发者关系部门、产品管理部门和工程部门的代表，以确定此列表的优先顺序。当新项目进入队列时，我们会根据其它项目的相对优先级定期对它们进行排位。当工作完成后，项目就会在队列中向上移动。

Angular receives a large number of feature requests, both from inside Google and from the broader open-source community. At the same time, our list of projects contains plenty of maintenance tasks, code refactorings, potential performance improvements, and so on. We bring together representatives from developer relations, product management, and engineering to prioritize this list. As new projects come into the queue, we regularly position them based on relative priority to other projects. As work gets done, projects will move up in the queue.

下面这些项目并没有关联到特定的 Angular 版本。我们会在完成时发布它们，它们会根据我们的发布计划，并遵循语义化版本规范，变成特定版本的一部分。例如，当完成各种特性后会在下一个次要版本中发布，如果包含重大变更，则会到下一个主版本中发布。

The projects below are not associated with a particular Angular version. We'll release them on completion, and they will be part of a specific version based on our release schedule, following semantic versioning. For example, features are released in the next minor after they are complete, or the next major if they include breaking changes.

进展中link

In Progresslink

Accelerated debugging and performance profiling with Angular DevToolslink

We are working on development tooling for Angular that will provide utilities for debugging and performance profiling. This project aims to help developers understand the component structure and the change detection in an Angular application.

Improve test times and debugging with automatic test environment tear downlink

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.

Deprecate and remove IE11 supportlink

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 collected feedback from the community and decide on next steps to move forward.

Leverage ES2017+ as the default output languagelink

Supporting modern browsers will allow us to leverage the more compact, expressive, and performant new syntax of JavaScript. As part of this project we’ll investigate what are the blockers to move forward with this effort and take the steps forward to enable it.

改进性能仪表盘来检测性能退化link

Revamp performance dashboards to detect regressionslink

We have a set of benchmarks that we run against every code change to ensure Angular aligns with our performance standards. To ensure the framework’s runtime does not regress after a code change, we need to refine some of the existing infrastructure the dashboards step on.

Enhanced Angular Material components by integrating MDC Weblink

MDC Web is a library created by Google's 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 will align Angular Material more closely with the Material Design specification, expand accessibility, improve component quality, and improve our team's velocity.

Angular component accessibilitylink

We're evaluating components in Angular Material against accessibility standards such as WCAG and working to fix any issues that arise from this process.

Remove legacy View Enginelink

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.

Publish guides on advanced conceptslink

Develop and publish an in-depth guide on change detection. Develop content for performance profiling of Angular applications. 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.

更新我们的 e2e 测试策略link

Update our e2e testing strategylink

为了确保我们能提供面向未来的 e2e 测试策略，我们希望评估 Protractor 的状态、社区的创新、e2e 最佳实践，并探索新的机会。

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.

Angular 库使用 Ivylink

Angular libraries use Ivylink

在 2020 年早些时候，我们共享了一个用于 Ivy 库发布方式的 RFC。经过社区的宝贵反馈，我们开发出了该项目的设计方案。我们现在正致力于 Ivy 库发布方式开发，包括更新库包的格式，以便使用 Ivy 编译，继续推进弃用 View Engine 库格式以及 ngcc。

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.

Ensure smooth adoption for future RxJS changes (v7 and beyond)link

We want to ensure Angular developers are taking advantage of the latest capabilities of RxJS and have a smooth transition to the next major releases of the framework. For this purpose, we will explore and document the scope of the changes in v7 and beyond RxJS and plan an update strategy.

Futurelink

Investigate micro frontend architecture for scalable development processeslink

Look into independent deployability and development of large-scale applications to improve efficiency and productivity. The Angular community has an established story for micro frontend support. As part of this effort, we’d investigate what would be the correct abstractions to provide better support.

通过为 @angular/forms 实现严格类型化来提升开发效率link

Better developer ergonomics with strict typing for @angular/formslink

我们将努力为响应式表单实现更严格的类型检查。这样，我们就可以让开发人员在开发期间捕获更多的问题，提供更好的文本编辑器和 IDE 支持，并改进对响应式表单的类型检查。

We will work on implementing stricter type checking for reactive forms. This way, we will allow developers to catch more issues during development time, enable better text editor and IDE support, and improve the type checking for reactive forms.

提升无 Zone.js 方案的完整框架能力link

Leverage full framework capabilities with Zone.js opt-outlink

We are going to design and implement a plan to make Zone.js optional from Angular applications. This way, we will simplify the framework, improve debugging, and reduce application bundle size. Additionally, this will allow us to take advantage of native async/await syntax, which currently Zone.js does not support.

将 ngc 作为 tsc 的插件，以提高构建性能link

Improved build performance with ngc as a tsc plugin distributionlink

将 Angular 编译器作为 TypeScript 编译器的插件进行发布，可以大大提高开发人员的构建性能，降低维护成本。

Distributing the Angular compiler as a plugin of the TypeScript compiler will substantially improve developers' build performance and reduce maintenance costs.

支持向宿主元素添加指令link

Support adding directives to host elementslink

一项由来已久的特性请求是增加为宿主元素添加指令的能力。该特性允许开发人员使用额外的行为来扩展自己的组件，而不必使用继承。该项目在定义 API、语义和实现方面都需要付出巨大的努力。

A long-standing feature request is to add the ability to add directives to host elements. The feature will allow developers to augment their own components with additional behaviors without using inheritance. The project will require substantial effort in terms of the definition of APIs, semantics, and implementation.

通过可选 NgModule 来简化 Angular 的心智模型link

Simplified Angular mental model with optional NgModuleslink

为了简化 Angular 的心智模型和学习之旅，我们将努力让 NgModule 成为可选项。这项工作将允许开发人员开发独立的组件，并实现另一种 API 来声明组件的编译范围。

To simplify the Angular mental model and learning journey, we’ll be working on making NgModules optional. This work will allow developers to develop standalone components and implement an alternative API for declaring the component’s compilation scope.

更符合工效学的组件级代码分割 APIlink

Ergonomic component level code-splitting APIslink

A common problem with web applications is their slow initial load time. A way to improve it is to apply more granular code-splitting on a component level. To encourage this practice, we’ll be working on more ergonomic code-splitting APIs.