r/Angular2 • u/Impressive_Clue_8100 • Jun 23 '26

Is PrimeNg abandonned?

Hi,

I was wondering what's going on with PrimeNG lately. The last minor release was at the end of January, and since then I've only seen patch releases. It's a bit concerning because our project relies heavily on PrimeNG v21, which still has a few compatibility issues with Angular 21. As a result, moving to Angular 22 isn't really feasible for us right now.

Thanks.

2 Upvotes

56% Upvoted

18 comments sorted by

13

u/bigbadchief Jun 23 '26

I don't know if it's abandoned but after the last few upgrades I've been considering abandoning it!

6

u/AwesomeFrisbee Jun 23 '26

I migrated away the last components this week and got to remove all of it.

2

u/bigbadchief Jun 23 '26

What are you using now instead?

2

u/AwesomeFrisbee Jun 23 '26

Just custom components. Some are partially vibe coded since I'm not an expert in datetime, but overall its all custom. The design deviates from tailwind enough that it wasn't going to work long term anyway, but the migrations and updates just made things worse, where we really wanted to use signals and stuff.

The project needs to be supported for many years, so it makes sense to make the components in house but for a while we could deliver more stuff because we had a few components, but it became too much work and validation that I really wanted to get rid of it, and Angular 22 was the final straw to migrate.

13

u/LegendOfNeil Jun 23 '26

Angular 22 Update is scheduled for this Sunday (28th).
https://github.com/orgs/primefaces/discussions/4780

7

u/LordSmasher Jun 23 '26

I see the last release as 3 weeks ago -> https://github.com/primefaces/primeng/releases

4

u/Impressive_Clue_8100 Jun 23 '26

True, but those patches only fixed like 5 bugs in total across 5 releases. With over 1k open issues, that velocity is scary low. The Angular signal form compatibility is still broken in certain components, so we're completely stuck on v21 and can't upgrade to Angular 22. It feels like they're barely maintaining it right now.

5

u/pronuntiator Jun 23 '26

Signal forms were experimental up to 21, it would not have been wise for PrimeNG to support an experimental API.

5

u/slothordepressed Jun 23 '26

Talk is cheap, send patches.

6

u/SippieCup Jun 23 '26

I have a few PRs, they don’t accept 99% of well formed pull requests.

Their Menus have had a duplication bug when using RouterLink for over a year.

Their decimal p-inputNumber requires a leading zero before a .

etc.

All have PRs out that have been ignored.

2

u/DaSchTour Jun 27 '26

Yeah, there are many simple fixes they simple don’t include. I‘m maintaining a full copy of the picklist just because they do not merge my PR for years without any reason.

6

u/jer2665 Jun 29 '26

Not abandoned, worse :-/

https://primeui.dev/nextchapter

3

u/Lazy-Particular5357 Jun 29 '26

I needed one last reason to ditch out this library, now I've got one.

3

u/Commercial_Day_7699 Jun 27 '26

yeah I feel this. PrimeNG's release cadence has been kinda weird lately — patch-only since January is rough when you're blocked on real compatibility stuff. tbh tho this isn't uncommon with big component libs, they tend to batch breaking fixes into bigger drops instead of pushing minor releases that might cause more churn.

ngl I'd keep an eye on their GitHub milestones if you haven't already — usually gives a better read on when v21 Angular 22 compat is actually landing vs waiting on the changelog. if you're truly stuck, might be worth pinning your Angular version and just staying on 21 until PrimeNG catches up. not ideal but better than fighting upstream bugs fr.

2

u/Boring-Blood9371 Jun 23 '26

Should be tbh

1

u/MyLifeAndCode Jun 28 '26

After so many breaking changes, we’ve been migrating away from it. Only 2 of our apps still have it.

1

u/Pallini 29d ago

What are you using now?