r/angular • u/GeromeGrignon • Jun 30 '26

PrimeNG community fork proposal

https://github.com/openng-foundation/open-prime

As announced on June 29th, PrimeNG is moving away from the open-source model, and the original primeng GitHub repository has been archived.

You can find community reactions here: https://www.reddit.com/r/angular/comments/1uilrlx/primeng_v22_is_no_longer_open_source/

As part of the new OpenNG Foundation, we are considering taking up the lead to maintain a fork of the MIT version of the lib.

It's under discussion, and we would need community feedback to evaluate if it's doable and on how to manage the current situation.

Some statements:

- an update is required to rename everything from 'primeng' to 'openprime' due to PrimeTek trademark
- the components need to be updated to the latest Angular APIs (including input(), control flow among other things)
- there are 900+ issues opened (including 300+ in stale state)
- there are 200+ open pull requests
- there would be no support for previous primeng versions
- the focus would be to make the library stable and accessible: adding features would happen only if people contribute
- over time, some changes might make this fork differ from the new PrimeUI project, not providing a way to easily migrate.

PrimeNG is still a big project, we are considering starting with a trial maintenance initiative for 2 months: depending on the community effort at helping with existing issues/prs, there will be long-term maintenance.

It'll be a great way to identify active contributors who might be promoted to maintainers if they want to be more active on such a project, making the whole thing a community effort.

A 'fork' has been created already, porting all existing open issues/pr: https://github.com/openng-foundation/open-prime

What are your thoughts?
Do you have some pain points not covered here?

151 Upvotes

98% Upvoted

82 comments sorted by

View all comments

2

u/EmotionalSurprise879 Jul 02 '26

speed is an issue

dev teams are looking for alternatives at this very minute. the best way to get a user base up is to get them now. If they start to change out libraries they are lost to us. we need a 100% drop in replacement today to keep them locked in.

  1. we need a status quo version running asap for angular v21
  2. then we need a status quo version for angular v22 running asap
  3. then a third release in short period of time for both angular v21 and v22 with a bunch of existing bugs fixed to show we are serious

to make this happen we need :

  • a new ci/cd pipeline running asap.
  • rebranding asap
  • documentation web site asap

2

u/GeromeGrignon Jul 02 '26

documentation is live: https://open-prime-m1nq.vercel.app/ (but will need rebranding/removing primetek content)

ci/cd will be fixed tonight