Skip to content
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

Closed
1 of 4 tasks
rpastro opened this issue Feb 20, 2025 · 11 comments
Closed
1 of 4 tasks

PrimeNG not working after upgrade to Angular 19.1.7 #17730

rpastro opened this issue Feb 20, 2025 · 11 comments
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@rpastro
Copy link

rpastro commented Feb 20, 2025

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

  • Lack of time
  • Unsure how to implement the fix/feature
  • Difficulty understanding the codebase
  • Other

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

@rpastro rpastro added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 20, 2025
@ruslan-khomiak
Copy link

I have the same issue

@Farbfetzen
Copy link

Duplicate of #17716

@Viktor-Ivliev
Copy link

I have the same issue, with error for some primeng components:

./node_modules/primeng/fesm2022/primeng-tooltip.mjs:769:54-81 - Error: export 'ɵɵInputTransformsFeature' (imported as 'i0') was not found in '@angular/core' (possible exports:

@tsteuwer-accesso
Copy link

tsteuwer-accesso commented Feb 20, 2025

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.

@aryanisml
Copy link

aryanisml commented Feb 21, 2025

I have use the following website to see the prime ng component - https://primeng.org/installation. I am using angular
angular19-project@0.0.0 /Users/swapnilkamble/ag19/angular19-project
├─┬ @angular/animations@19.1.7
│ └── @angular/core@19.1.7 deduped
├─┬ @angular/common@19.1.7
│ └── @angular/core@19.1.7 deduped
├─┬ @angular/compiler@19.1.7
│ └── @angular/core@19.1.7 deduped
├── @angular/core@19.1.7
├─┬ @angular/forms@19.1.7
│ └── @angular/core@19.1.7 deduped
├─┬ @angular/platform-browser-dynamic@19.1.7
│ └── @angular/core@19.1.7 deduped
├─┬ @angular/platform-browser@19.1.7
│ └── @angular/core@19.1.7 deduped
├─┬ @angular/router@19.1.7
│ └── @angular/core@19.1.7 deduped
└─┬ primeng@19.0.6
├─┬ @angular/cdk@19.1.5
│ └── @angular/core@19.1.7 deduped
└── @angular/core@19.1.7 deduped

└── 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
at core.mjs:19348:38
at Array.forEach ()
at initFeatures (core.mjs:19348:24)
at Object.toString (core.mjs:19291:5)
at noSideEffects (core.mjs:122:5)
at ɵɵdefineDirective (core.mjs:19289:10)
at <static_initializer> (primeng-autofocus.mjs:63:33)
at primeng-autofocus.mjs:11:25

@imaksp
Copy link
Contributor

imaksp commented Feb 21, 2025

Hi @aryanisml , you need to downgrade Angular version to 19.1.6 until this is fixed, you can use fixed version (remove ^) in package.json for this.

@aryanisml
Copy link

Hi @aryanisml , you need to downgrade Angular version to 19.1.6 until this is fixed, you can use fixed version (remove ^) in package.json for this.

Thanks.
It seems the issue of Angular side.

@rpastro
Copy link
Author

rpastro commented Feb 21, 2025

Hi @aryanisml , you need to downgrade Angular version to 19.1.6 until this is fixed, you can use fixed version (remove ^) in package.json for this.

Thanks. It seems the issue of Angular side.

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

@cetincakiroglu cetincakiroglu added this to the 19.0.7 milestone Feb 21, 2025
@github-project-automation github-project-automation bot moved this to Review in PrimeNG Feb 21, 2025
@mertsincan
Copy link
Member

@rpastro
Copy link
Author

rpastro commented Feb 21, 2025

@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."

@rpastro
Copy link
Author

rpastro commented Feb 21, 2025

Should be fixed with #17731

@rpastro rpastro closed this as completed Feb 21, 2025
@github-project-automation github-project-automation bot moved this from Review to Done in PrimeNG Feb 21, 2025
@mertsincan mertsincan added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
Status: Done
Development

No branches or pull requests

9 participants