5 lines
19 KiB
JSON
5 lines
19 KiB
JSON
|
{
|
|||
|
|
"id": "guide/roadmap",
|
|||
|
|
"title": "Angular Roadmap",
|
|||
|
|
"contents": "\n\n\n<div class=\"github-links\">\n <a href=\"https://github.com/angular/angular/edit/master/aio/content/guide/roadmap.md?message=docs%3A%20describe%20your%20change...\" aria-label=\"Suggest Edits\" title=\"Suggest Edits\"><i class=\"material-icons\" aria-hidden=\"true\" role=\"img\">mode_edit</i></a>\n</div>\n\n\n<div class=\"content\">\n <h1 id=\"angular-roadmap\">Angular Roadmap<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/roadmap#angular-roadmap\"><i class=\"material-icons\">link</i></a></h1>\n<p>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.</p>\n<p>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.</p>\n<h2 id=\"in-progress\">In Progress<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/roadmap#in-progress\"><i class=\"material-icons\">link</i></a></h2>\n<h3 id=\"faster-apps-by-inlining-critical-styles-in-universal-applications\">Faster apps by inlining critical styles in Universal applications<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/roadmap#faster-apps-by-inlining-critical-styles-in-universal-applications\"><i class=\"material-icons\">link</i></a></h3>\n<p>Loading external stylesheets is a blocking operation, which means that the browser can’t start rendering your application 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 <a href=\"https://web.dev/first-contentful-paint/\">first contentful paint</a>. To make apps faster, we’ve been collaborating with the Google Chrome team on inlining critical CSS and loading the rest of the styles asynchronously.</p>\n<h3 id=\"improve-debugging-with-better-angular-error-messages\">Improve debugging with better Angular error messages<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/roadmap#improve-debugging-with-better-angular-error-messages\"><i class=\"material-icons\">link</i></a></h3>\n<p>Error messages often bring limited actionable information to help developers resolve them. We’ve been working on making error messages more discoverable by adding associated codes, developing guides, and other materials to ensure a smoother debugging experience.</p>\n<h3 id=\"revamp-performance-dashboards-to-detect-regressions\">Revamp performance dashboards to detect regressions<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/roadmap#revamp-performance-dashboards-to-detect-regressions\"><i class=\"material-icons\">link</i></a></h3>\n<p>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.</p>\n<h3 id=\"update-our-e2e-testing-strategy\">Update our e2e testing strategy<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/roadmap#update-our-e2e-testing-strategy\"><i class=\"material-icons\">link</i></a></h3>\n<p>To ensure we provide a future-proof e2e testing strategy, we want to evaluate the state of Protractor, commu
|
|||
|
|
}
|