-
Notifications
You must be signed in to change notification settings - Fork 130
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
Angular 11 support #148
Comments
Please, suport it! ❤️ |
Is there something unique to this implementation that requires angular 10.x? |
did someone find any workarounds for this issue? |
I've just upgraded Angular from 10 to 11. "npm install" warns me about the broken requirement, but application works nonetheless (keep alive, pings, etc.). However, yes, would be nice to have dependency updated. |
Is this PR enough to resolve this, or is there more work needed? What can we do to get this completed? |
The project is looking for a maintainer though. I don't know if the current maintainer has much time to even look at the issues. |
Any updates on upgrading the plugin to support latest Angular 12+? |
Seems these issues are ignored. After all this time may make sense to fork this repo and release a separate package. |
Hey @NateRadebaugh why don’t you fork it and we all can use your fork? You’re right. This repo seems to be dead at all… we all coul maintain it |
#97 is a pinned topic about needing a new maintainer if you want to get involved. I'll also accept a pull request for Angular 11 support. Someone is working on 12. |
Thanks @moribvndvs we'll track next steps with @worksoncloud since it looks like he's the newly appointed maintainer. [Edit] looks like the PR with support for Angular 12 is here: #151 |
#151 has been merged and this has all been released as 11.0.3 |
Any plans of upgrading the plugin to support Angular 11?
The text was updated successfully, but these errors were encountered: