-
Notifications
You must be signed in to change notification settings - Fork 96
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
Is this being maintained? #36
Comments
I'm calling it... this project has been abandoned. No updates on this ticket for 60 days. Maybe that's the new protocol to find out if a project is abandoned. Create a bug saying if a dev doesn't respond in 30-60 days that its officially abandoned. |
In case anyone is still looking for a solution for this, I recommend my approach that I posted here: https://gist.github.com/gragland/2970ae543df237a07be1dbbf810f23fe#gistcomment-3459041 If anyone wants to grab that and make it a full repo and npm package fine by me. Otherwise one day I may get a chance to do that myself. |
use-local-storage-state author here. I have been developing similar functionality. I have been actively maintaining it for 7 months now so I welcome everybody. Update 25 November 2021: I've been consistently working on use-local-storage-state for a year and a half now. You can see the contributions graph. |
A new update has been released since @burtonator pronounced it dead. Could a maintainer please close this ticket? It's creating FUD. |
@callumlocke can we FUD now? |
@donavon There hasn't been a new version in 2 years and people have reported bugs in issues. That's a shame since this package has over 44,000 weekly downloads according to npm.
When could we expect to see anymore development? Is this abandoned?
The text was updated successfully, but these errors were encountered: