PrimeNG is shifting its licensing model, while A2UI emerges as a way to let AI models drive Angular interfaces — those are the main stories this round.
Elsewhere: OpenNG has launched a community fork of PrimeNG, a new router resource behavior is in the works, and the micro-frontend tooling landscape for Angular keeps evolving.
PrimeNG's Licensing Shift
PrimeNG, a widely adopted UI component library, has revealed that upcoming major releases will no longer ship as open source. Instead, they'll be offered under a free Community license aimed at individuals, students, non-profits, non-commercial open source projects, and smaller organizations.
This change applies to the Angular, React, and Vue versions alike. The reasoning: as the library has matured, maintaining it as a purely open source effort has become increasingly demanding. At a certain point, revenue from peripheral products no longer covered the ongoing development costs.
The new licensing umbrella is called PrimeUI. The introductory price is USD 599 per developer, which is a perpetual license for the covered versions and includes one year of updates. It also bundles PrimeUI PRO, which adds components for charts, a text editor, a scheduler, a task board, and more. These Pro components are excluded from the Community license.
In response, OpenNG — an organization that steps in to maintain abandoned libraries — has noted that PrimeNG went closed-source, with its GitHub repository archived on June 28th, 2026. OpenNG has created a copy of the project, complete with regenerated open issues and pull requests. Their objective is to ship a beta release that supports Angular 22. This is effectively a fork. At the moment, it goes by the name `open-prime`, though OpenNG acknowledges the name is too similar to PrimeNG given PrimeTek's planned trademark efforts.
A2UI
Devin Chasanoff from the Angular team has published an article demonstrating how to use A2UI with Angular. This approach enables dynamic user interfaces that are steered by an AI model.
Here's how it works: the user conveys an intent through the frontend. That intent, along with relevant context, is forwarded to a model. The communication can also include a component catalog that the frontend is capable of rendering. Based on that, the model decides whether UI components are necessary, which ones fit the request, and then returns structured UI instructions back to the application.
A2UI is the protocol designed for these agent-generated UI scenarios. The messages can travel over HTTP, WebSocket, or Server-Sent Events, depending on how the application is architected.
Demystifying A2UI: How to Make AI Agents “Speak UI” in Your App
routerResource
In other developments, it looks like work has started on connecting resource behavior with the router. A pull request meant for internal use has appeared, introducing a snapshot-based router resource behavior to integrate navigation-specific details.
This snapshot would lock a resource's state — for instance, its current value — during a navigation. If the navigation completes successfully, the underlying value is revealed. If it gets cancelled, the frozen value stays in place for rollback recovery.
Consider this scenario. A resource takes a router parameter as its own input, like a product id that triggers loading a product by that id. If the user stays on the same component but navigates to a different product id, the resource would typically change state right away, and the UI would update mid-navigation. That can lead to flickering, especially if a guard cancels the navigation and the product id reverts to its original value.
With the new router resource behavior, that won't occur. It's worth noting the PR description explicitly states this isn't exposed for public use right now, but it's a strong signal that resources and the router will eventually be integrated.
Micro-Frontends
Elsewhere, adopting micro-frontends is an architectural requirement that shows up frequently in enterprise settings. While not a built-in Angular framework feature, two common community solutions exist: Native Federation and Module Federation.
The core difference in Angular is that Native Federation is built on esbuild, which is the modern Angular builder, whereas Module Federation traditionally relies on the older webpack builder or alternatives like Rspack.
Native Federation is maintained by Angular Architects, while Module Federation support in Nx has been a common choice for Angular workspaces. In the Nx 23 release notes, Nx now endorses `@angular-architects/native-federation` for Angular projects and marks the older Nx-specific Module Federation generators and executors as deprecated.
Nx 23: 4x Faster Nx Agents, Agentic Nx Migrate, improved targetDefaults, .Net GA | Nx Blog
Ng-News 26/17: PrimeNG’s New Licensing, and A2UI for Angular was originally published in ng-news on Medium, where people are continuing the conversation by highlighting and responding to this story.