-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PrimeNG not working after upgrade to Angular 19.1.7 #17730
Comments
I have the same issue |
Duplicate of #17716 |
I have the same issue, with error for some primeng components:
|
Arg. I just posted this over on Angular's issue tracker. What's interesting is that I'm not entirely sure this is PrimeNG's issue but i guess it could be. You can view my findings over on that issue. Update Nevermind, Angular confirmed PrimeNG is precompiling stuff instead of letting it be done on the app side. |
I have use the following website to see the prime ng component - https://primeng.org/installation. I am using angular └── primeng@19.0.6 getting the error even added normal button component which mentioned on ngPrime site . Any one can provide more on this core.mjs:19348 Uncaught TypeError: fn is not a function |
Hi @aryanisml , you need to downgrade Angular version to |
Thanks. |
If you look at the description of this issue you'll see that Angular team has already analyzed this and they indicated the problem is with PrimeNG, which is publishing precompiled code instead of partially compiled code. You can see the analysis at angular/angular#60033 |
@mertsincan See https://angular.dev/tools/libraries/creating-libraries#ensuring-library-version-compatibility "Avoid compiling libraries with full-Ivy code if you are publishing to npm because the generated Ivy instructions are not part of Angular's public API, and so might change between patch versions." |
Should be fixed with #17731 |
Describe the bug
Application using PrimeNG no longer loads after upgrade to Angular 19.1.7. An issue was opened against Angular, but was closed as works as designed indicating the issue is with PrimeNG, which is publishing precompiled code instead of partially compiled code.
See angular/angular#60033
Pull Request Link
No response
Reason for not contributing a PR
Other Reason
No response
Reproducer
https://stackblitz.com/edit/stackblitz-starters-nxtcukvt
Environment
Any environment
Angular version
19.1.7
PrimeNG version
19.0.6
Node version
22.14.0
Browser(s)
Chrome
Steps to reproduce the behavior
See https://stackblitz.com/edit/stackblitz-starters-nxtcukvt
Expected behavior
No crash
The text was updated successfully, but these errors were encountered: