-
Notifications
You must be signed in to change notification settings - Fork 662
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
Support Angular 19 #1283
Comments
While I fully agree with the sentiment and look forward to the fix as well, the component seems to still be working for us on Angular 19 as long as I do force commands to ignore the dependency mismatches. I confess that I had been worried because of the NgModule usage and non-standalone directives with the new switch to standalone by default. I thought I had read somewhere that prior libraries would be handled gracefully but there's no substitute for actually running things. :) |
Can you just add |
Created pull request for this: #1284 |
When can we expect support for version 19? |
Meanwhile, I found the Comment which can possiblity solve issue for us. I have tried and it is working as of now. |
When can we expect this package getting updated to support Angular 19? We migrated our project to Angular 19 and are facing issues with this particular package. As of now, we were using version 7.0.1 which supports Angular 18
The text was updated successfully, but these errors were encountered: