-
Notifications
You must be signed in to change notification settings - Fork 285
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
State of the project #164
Comments
I have spent the last day trying to make this library work for a NodeJS app as described in the documentation and have had no luck :( Not sure what I'm doing wrong. |
@mcdoolz I think your issue should be created as new issue here on github. |
I would also like to know the state of the project. It seems unreasonable that it has over 700k weekly downloads on npm at the time of this post. |
Hey @Dakine135. I'm no longer actively working on the project. The core project is "feature complete" meaning I wasn't intending to take it further down the path to being either a true database or a JavaScript framework. I wasn't aware of the heavy usage on npm. I'll look through the issues and see if I can address them (license in particular) although I'd happy to have help. Taffy predates any of my usage of NPM. |
Thanks for your quick response. It does seem odd for something that is fairly niche, and an abandoned project. |
It's 2023 and many third-party projects still rely on this package. It's unfortunate, but that is the reality. If you're discontinuing support for this project, how about passing the torch to someone who will? ✋ |
@nuxy are you saying you are interested? It could use the help… |
I would be interested. |
On the fence right now (leaning yes, I love challenges) but still reviewing the script logic, open issues, pull requests.. Based on my initial review the first course of action (road to stable) would be:
Will spend more time on this over the weekend. Will keep you posted. |
There were no updates since more than one year.
Please tell us the state of this project.
The text was updated successfully, but these errors were encountered: