u/GeromeGrignon

Optimus UI 2.0.0 is out.

The PrimeNG community fork now supports Angular 22!

That's a small release meant to jump from Angular 21 to Angular 22.
We'll now start addressing the 900 existing open issues and reviewing community PRs.

This version also introduces 'ng update' support, so you can update all your Optimus UI sub packages at once, and it'll unlock the ability to provide migration schematics if needed in the future!

Check out the update guide: https://optimus.openng.org/migration/update

Community members created a fork of PrimeReact (as Prime projects went closed-source on June 28th).

Mantle UI is an independent, community-maintained React UI component library based on the MIT-licensed PrimeReact v10 codebase.

The project exists to provide PrimeReact v10 users with a stable, open-source path forward. Mantle UI preserves the familiar component APIs and development model while continuing maintenance, bug fixes, accessibility improvements, documentation, and compatibility work in the open.

Mantle UI is not affiliated with PrimeTek, PrimeReact, or ngrok.

Find out more on GitHub: https://github.com/Mantle-UI/mantle-ui

PS: I'm not affiliated with the project myself (working on PrimeNG fork), you can contact maintainers through GitHub or their Discord server directly.

We just released the first release candidate version for the PrimeNG community fork!

Two big news at once:

Based on the feedback we got, we chose to rename the project 'Optimus UI'.

This first version targets Angular v21 projects to ensure compatibility with the latest MIT PrimeNG version.

It includes ng add support and a schematic to handle the migration.

So you can use it on both new and existing projects.

The migration will rename references (due to trademarks with PrimeNG) and imports (as we are taking over all required PrimeNG sub packages too).

You can test it out with the installation explained here: https://www.npmjs.com/package/@openng/optimus-ui?activeTab=readme

Feedbacks are very welcome so we can publish a stable version soon.

The new documentation is live here: https://optimus.openng.org/

EDIT:

We got positive feedback so far, we need to support two more packages (primelocale and tailwindcss-primeui), as we not only ported the original PrimeNG project but all its dependencies too.

The Angular team is currently updating its release policy to move to:

- A major release every 12 months

- 4-6 minor releases for each major release

PR link: https://github.com/angular/angular/pull/69817

As people have questions about the future of projects such as Spectator or PrimeNG, here is the current state of our actions.

OpenNG

We just renamed the initiative from OpenNG Foundation to OpenNG to avoid confusion and follow the trademark policy with the OpenJS Foundation organization.

Funding

We are working on a funding model to support the maintenance of the projects and give back to contributors. We submitted the initiative to Open Collective and contacted HeroDevs for partnership.

Versioning Policy

We'll start over with v1.0.0 for all the packages. Each project will include a matrix compatibility table with the supported major Angular versions (including the previous package). Some packages were already not following the Angular versioning policy, and it will allow us to author a major version for breaking changes anytime.

PrimeNG

PrimeNG went closed-source, and the GitHub repository was archived on June 28th, 2026. Discover the announcement here.

We created a copy of the project and regenerated the open issues/PRs. Out of 968 open issues, 58 have already been closed, and 23 triaged as still relevant and accepting contributions to resolve them. Triaging was made possible thanks to the contribution of the community.

Our goal this week is to release a beta version supporting Angular 22, as people were already delaying updating their projects. It'll include:

• a set of unreleased changes from the original repository (modernize existing components, add a few new ones)
• ng add support for new projects
• ng update support as unreleased changes include a few breaking changes (camelcase selectors removed, deprecated APIs removed)

Our current blocker for this release is to find a proper name for the project. Currently named open-prime, it's too close to PrimeNG as PrimeTek plans to put trademarks on it. We asked the community for suggestions here.

We are currently evaluating proposals, with the main restriction being not adding confusion with another project (there are a lot of UI frameworks matching proposals).

ngneat projects

Out of the 34 original repositories, we decided to start working on the following ones:

• cashew
• query
• elf
• spectator

We have a volunteer working on cashew, currently preparing the first release.

Spectator is our priority within the ngneat ecosystem, planning a release this week. We also have a contribution to expose the jasmine package as a standalone (like jest/vitest ones, planned to land in 1.1.0.

We still need to triage the remaining repositories to understand if we should keep them or not. 13 of them might not be maintained anymore due to low activity or having a better alternative nowadays.

GitHub: https://github.com/openng-org

Hey everyone!

As shared in the sub over the last days, PrimeNG transitioned away from its traditional open-source model.

We started working on atruly community-governed, MIT-licensed alternative, 'open-prime' (https://github.com/openng-foundation/open-prime).

As we set up our foundations, the original creators reached out with a very reasonable and friendly request: to drop the "Prime" branding to avoid any future copyright or trademark confusion as they process their product suites.

We want to use this as an opportunity to give this project its own unique, powerful identity—and we want the community to build it with us.

Here are a few directions we are thinking about:

The Successor Route: (e.g., ApexNG, OptimaNG) — Professional, premium-sounding independent names.

The OSS Roots Route: (e.g., LibreNG, CivicNG) — Highlighting community ownership.

The Visual/UI Route: (e.g., PrismNG) — Phonetically similar, clean, and relates to UI components.

Share your thoughts and drop your own suggestions!

Still having no news from the ngneat organization, I decided to revive an old idea, to create a foundation for Angular open-source projects, to help govern/maintain them.

The GitHub Organization, OpenNG Foundation, is still empty.

Our priority will be to fork and revive key, unmaintained Angular projects to ensure they stay secure, updated, and community-driven.

Always landing on unmaintained Angular example apps or just willing to try out a new version/lib/feature without bootstrapping a whole new app, I just released this new 'Realworld Angular' playground.

I maintained the original RealWorld project for years, only to find out it was quite limited in being strict with the specs and hard to assert quality projects.

This new open-source project is only focused on Angular. You can run the project locally, fork it, and it's pretty unique as it's provided with a real API you can use for free: the project is not limited to using data mocks and not exploring all aspects of a real-world application.

Give it a try: https://github.com/realworld-angular/realworld-angular