Angular 19 & PrimeNG 17.19 ?

[djay1977]

Hello,
Would it be possible to release a version 17.19 of PrimeNG compatible with Angular 19 ?
The migration time to the new version with Design Tokens and TailwindCSS may take us a lot of time.

Thanks in advance

[AStoker]

Linking related items:
primefaces/primeng#16783

Angular 19 changed the way the standalone feature works, making libraries compiled in previous versions of angular incompatible with angular 19 projects.

[utillity]

So @AStoker will there be a release so we can switch to ng19 anytime soon?

[AStoker]

My mistake for misunderstanding your original question @djay1977. Unfortunately, even with version 18 of PrimeNG, it does not support Angular 19.
Because of the way the builds work with Angular, there would have to be a fair amount of refactoring to get an Angular 19 supported version of PrimeNG 17 (at least from what I saw). As this is the open source world, I don't see a reason somebody couldn't take that task on themselves and try to make a PR.
@utillity, I'm not on the PrimeNG team, so I really don't know. This was just all from my digging into it over a day (because I really wanted to use angular 19, and wanted to know what was broke 😂 ). This is the defect they're using to track adding Angular 19 support: primefaces/primeng#16827
Best bet is to follow it there on any timeline.

[raboud]

I would be willing to checkout how to migrate v18 of primeNG to Angular 19 if I had a clue which branch to use...Master, Prod, V18, v18-prod

I've tried v18 with Angular v19 and i get an exception in p-floatlabel.

[djay1977]

You just need to publish a 17.19 and specify in the dependencies for Angular: ^17.0.0 || ^18.0.0 || ^19.0.0
The version 17.18.12 works correctly with Angular 19 but not v18 without forgetting all the refactor that it imposes with the Design Tokens, TailwindCSS and the breaking changes

[awardhan11]

@djay1977

Did you do anything different to make PrimeNG version 17.18.12 works with Angular 19 ?
Or just out of the box ?

Thanks,

[djay1977]

It works perfectly, just do a "npm i --force" for peer dependencies issues with the Angular version.

[awardhan11]

Thanks,...