-
Notifications
You must be signed in to change notification settings - Fork 15
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
Maintenance #22
Comments
Hi @simeonborko! I don't have time to update this anymore and I also don't work for the company that owns this github org. I would suggest that you fork this project and update it there and the I'll happily edit the readme here to point users at your fork and say that this is the newer version. |
Thanks for the answer, I'll prepare it and let you know. Then we should also transfer package on npmjs.com, if possible. |
Hello @danyx23, My fork is here: https://github.com/loschmidt/jsme-react/ Would you mind to transfer package on npmjs.com to my account? https://www.npmjs.com/~simeonborko |
Hi @simeonborko! I just wanted to transfer that package to you but I no longer have access to the account that owns it. I used to be able to log into that account for a while after I stopped working there but it seems someone invalidated my credentials. I don't know who at the company, by now called Edelweiss Connect, is responsible for this now or if they would reply to any such requests. Maybe the best you can easily do is just signpost here the name of your new package? This thread is probably something people would find when they look for newer versions. Sorry that I can't help more! |
I see. I published it as |
Hello,
this package is apparently outdated. Are there any plans to maintain it and update to the current version of React?
I'm willing to do that. Otherwise I may create my own library, but it might be a pitty to put this to death.
@danyx23
@svaraborut
The text was updated successfully, but these errors were encountered: