Closed tsenguunchik closed 6 months ago
Dear all, This update is very welcomed by my team as well. We are looking forward to it too.
Is there any temporal workaround?
Is there any temporal workaround?
This version is still working for my v17 project. It would be just nice to get the support
While I'm hoping for proper ng17 support, I guess that making this work in an module-less environment might require a significant rewrite. Meanwhile this is working fine in my ng17 app. I even can npm i without --force
Hi all
I will work on this on this weekend. Please bear with me, as this is a project that I'm maintaining on my free time, which is not that much
Thanks
PRs are also welcome :)
As title