Looking for a MAINTAINER(S) for this repo ❤️

[limonte]

Recently, this repo didn't get the amount of attention that is deserves. In the past it was @toverux who started the whole thing and put the great effort into the maintenance, but I guess he's busy now or switched the tech stack.

@rdamazio has put some effort into adding the Angular 19 support #268, he summarized quite well the tech debt:

it uses too many deprecated features (like dynamically creating components outside an injection context, ComponentFactoryResolver, zone-testing, non-standalone components, CommonModule, etc.), and all the dependencies are very old by now (last update was 2y ago?). Angular dependencies were updated over time up to v16 (and claimed compatibility to v18), but without updating the code for it.

If you someone who is familiar with this plugin and would like to put some effort into maintaining it, please let me know in this thread 🙌

Hopefully, I won't have to archive it 😢

Thank you ❤️

[FACode]

Hey @limonte, this package is awesome and it's a shame to not have complete support for Angular.

I can be the maintainer for it.
The latest Angular 19 update works well but there is still room for improvement.

• replacing the lib module with the latest Angular standards
• get rid of the standalone flags
• Update the docs/Readme
• plus more others

Let me know what you think. 🚀

@limonte 🤙

[limonte]

It would be great to have your help, thank you so much @FACode

There should be an invite to this repo in your notifications. After accepting it you will be able to create branches directly in this repo instead of your fork 🙌

Closing this issue, thanks again!

[limonte]

@FACode Releasing of new versions is happening automatically as long as we follow the commit conventions (chore, fix, feat).