docs: update the roadmap with our priorities at Q4 #39635
Conversation
|
|
||
| ### Refresh introductory documentation | ||
| As part of the v11 release, we introduced an opt-in preview of webpack 5 in the Angular CLI. To ensure stability, we’ll continue iterating on the implementation to enable build speed and bundle size improvements. |
There was a problem hiding this comment.
Can we mention this is experimental and only for yarn?
There was a problem hiding this comment.
I think opt-in preview is enough of a disclaimer. What do you think?
There was a problem hiding this comment.
Makes sense on experimental part, but many developers use npm and they may raise this as issue.
There was a problem hiding this comment.
We have instructions on enabling the preview in the blog post. I'd suggest keeping this outside the scope of the roadmap.
|
|
||
| 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. | ||
|
|
||
| ### Ergonomic component level code-splitting APIs | ||
|
|
||
| A common problem of 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. | ||
|
|
||
| ### Migration to ESLint |
There was a problem hiding this comment.
Is this done? or not on the immediate Roadmap anymore?
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Update the Angular roadmap.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?