Conversation
|
Bump. Can we get this merged in and published? It's quite annoying. |
|
Bump, merge this please! |
|
Agreed, would be nice to have this merged. |
|
Hey folks, I wrote this originally, but haven't been getting any emails about issues or pull requests. So I appologize for the delay. Right now this pull request doesn't make a ton of sense. The version of this library at this repository doesn't have sys required. Wondering if someone could help me figure out what @quangv is trying to merge this into. |
|
It looks like the currently published version is 0.1.1 and uses |
|
Well, I think the best path forward is probably to make this into a separate repository from mikeal's to start. If people want to use @quangv's fork as a starting point I'm fine with that, or I can work to publish the code that's here in a separate repository. After that we can push a new version to npm from there. I've changed jobs since I first published this and have a lot less time to hack on it. If after we get this sorted out someone else wanted to take up maintenance on it. It sounds like it's used and could use a more diligent caretaker than myself. Thoughts? |
|
Also I'll be in irc today, so if people want to help figure out a plan in real time that might be more effective than twitter and github comments :) |
|
I put up this repository https://github.com/aconbere/node-file-utils If folks wanted to help fix up that code base to fix lingering issues and changes that exist between it and @quangv's branch or maybe other forks that are out there either reply here, message me or whatever and we'll get you as editors of that project. |
get rid of silent warnings
related: #14