< img src="https://images.idgesg.net/images/article/2020/02/cia-triad_security_triangle-glowing_binary_process_by-nolimit46-getty_2400x1600-100831589-large.jpg?auto=webp&quality=85,70"alt=""> Now that Angular 15 has shown up, the designers of the Google-created, TypeScript-based web framework are considering enhancements to server-side making and runtime efficiency for a prepared Angular 16 release.Tentatively due in May 2023, Angular 16 would check out hydration and server-side rendering use enhancements, with an initial step being non-destructive hydration. This method would allow reuse of the server-side DOM, and instead of re-rendering it, would only connect event listeners and create data structures required by the Angular runtime.As a next step, plans call for more exploration of the dynamically developing area of partial hydration and resumability. Each approach has tradeoffs and Angular’s home builders
want to make an informed decision on an optimum, long-term solution.Hydration and server-side rendering use enhancements were noted on an Angular roadmap that was last upgraded November 5. Although those enhancements are not connected with a particular Angular variation in the
roadmap, a Google official today referred to them when asked what the plans were for Angular 16. Other features pointed out by Google for Angular 16 include the following: Reviewing Angular’s reactivity design and making Zone.js optional to improve runtime efficiency. Angular by default runs modification detection globally; alternatives are being examined to run change detection only in impacted elements. This streamlines the structure,
- Document refactoring, to guarantee all documentation suits
- a constant set of content types. Other efforts in progress but not mentioned by Google as prepared for Angular 16 include: Improving standalone imports with the language service, consisting of
- automatic importing of design template reliances for standalone parts.
- To make it possible for smaller sized application bundles, the language service will propose automatic elimination of unused imports
. New CDK(Part Dev Kit)primitives for developing custom elements based on the WAI-ARIA(Web Availability Effort Accessible Rich Web Applications)design patterns for Combobox. Features and enhancements on the roadmap however not necessarily in development consist of token-based theming APIs and making it possible for Material 3 capabilities; modernizing system testing; revamping efficiency dashboards