-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Add Angular 15 support #12243
Comments
Don't mind me just watchin 👀 |
Also it would be great to migrate components and directives to standalone versions to be able to use Directive Composition API and etc. |
Like and subscribe it :) wait it |
What are the plans about standalone components? |
@j-s-fesfwd Given how opinionated Angular is, I would be very surprised to see them using the Since standalone components are interop-able with normal ones, I'd speculate they will unblock people from being able to use v15 first before worrying about making them standalone which would come in a release at a later date. They could either introduce a breaking change and force every component to standalone, or they could include both module and standalone options (which seems like a pain to tree-shake and would probably require import changes). I guess we will see what the community does. If it becomes customary in the library community to provide both options, I reckon they will follow suit. However, I'm just speculating and would love to hear from a PrimeNG dev. Angular 15 is the hot topic right now, I'm sure they've got it covered. With such an integral library like PrimeNG is I'd imagine they will get an update out relatively quickly. |
🙌 🙌 🙌 YES Thank you @cetincakiroglu 🫡. You are the hero this world needed |
Happy to help, you're welcome :) |
Describe the bug
PrimeNG 14.2.2 is restricted to Angular < 15
Unable to update to Angular 15
Environment
Standard Angular / PrimeNG application.
Reproducer
No response
Angular version
15.0.0
PrimeNG version
14.2.2
Build / Runtime
Angular CLI App
Language
ALL
Node version (for AoT issues node --version)
18.12.1
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: