State of the project - Githubissues

typicaljoe / taffydb

TaffyDB - an open source JavaScript Database for your browser

http://taffydb.com

MIT License

2.21k stars 285 forks source link

State of the project #164

Open guettli opened 5 years ago

guettli commented 5 years ago

There were no updates since more than one year.

Please tell us the state of this project.

mcdoolz commented 4 years ago

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 :( Firing the return function for all rows as described simply returns the entire function (as it should). Any functions described are met with undefined.

Not sure what I'm doing wrong.

guettli commented 4 years ago

@mcdoolz I think your issue should be created as new issue here on github.

Dakine135 commented 3 years ago

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.

typicaljoe commented 3 years ago

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.

Dakine135 commented 3 years ago

Thanks for your quick response. It does seem odd for something that is fairly niche, and an abandoned project.

nuxy commented 1 year ago

@typicaljoe

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? :hand:

typicaljoe commented 1 year ago

@nuxy are you saying you are interested? It could use the help…

Dakine135 commented 1 year ago

I would be interested.

nuxy commented 1 year ago

@typicaljoe

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:

Replace the test suit (Mocha/Chai or equivalent) as I could not get the current test suite to work locally.
Unravel/refactor this ternary chain into smaller, manageable parts.
Add guards to resolve the Internal Property Tampering (open issue)

Will spend more time on this over the weekend. Will keep you posted.