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

Support Angular 19 #1283

Open
muminquadri opened this issue Dec 11, 2024 · 5 comments
Open

Support Angular 19 #1283

muminquadri opened this issue Dec 11, 2024 · 5 comments

Comments

@muminquadri
Copy link

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

@hamfastgamgee
Copy link

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. :)

@lopatnov
Copy link

Can you just add standalone: false to components and directives and into devDependencies Angular >18.0.2. It should work and fix could be quick.

@lopatnov
Copy link

Created pull request for this: #1284

@mm-srtr
Copy link

mm-srtr commented Dec 24, 2024

When can we expect support for version 19?

@mm-srtr
Copy link

mm-srtr commented Dec 24, 2024

Meanwhile, I found the Comment which can possiblity solve issue for us. I have tried and it is working as of now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants