search

aseemk / requireDir

Node.js helper to require() directories.
MIT License
484 stars 60 forks source link

Added 'ignore' option, tests for it and it's description in the README. #31

Closed bondden closed 6 years ago

bondden commented 8 years ago

Tried to follow the current code style and use ES5 for compatibility reasons.

trainerbill commented 8 years ago

can this merge? need an ignore or glob option

xinshangshangxin commented 8 years ago

when can merge it; i also need a ignore option, although I found another package to solve it

angelxmoreno commented 8 years ago

any plans to merge this?

xinshangshangxin commented 8 years ago

The auth Latest commit 824b9f1 on 24 Mar 2015; so I search another node-require-directory

sergiomichels commented 7 years ago

14 pending pull requests, I think it's time to try the node-require-directory indeed.

aseemk commented 7 years ago

Hey folks,

I'm sorry for my delay in responding to these issues and PRs. I've found it hard to find the time and motivation to maintain an active role in growing this project. The module has worked perfectly fine for my company in production for years now, and I've been hesitant to add features to it and risk making it bloated when it currently is nice and simple.

But I now realize that the module can still grow for other people's needs, and it shouldn't hurt us. I just can't commit to taking on the maintainer role anymore.

Is there anyone that's passionate and interested in maintaining this project? If so, I'll be happy to add you as a collaborator to this repo as well as to the package on npm. Let me know!

Thank you again for all your contributions.

Cheers, Aseem

yocontra commented 6 years ago

@aseemk I'll take it - I've been using this for years across a number of applications, but a few basic features (like this one) + maintenance would be nice.

aseemk commented 6 years ago

@contra: Invited. Thank you!

yocontra commented 6 years ago

Hi (new maintainer) - I've merged https://github.com/aseemk/requireDir/pull/27 which does the same thing, and was the first PR submitted to solve this problem. You should be able to achieve the same functionality with that. I'll be publishing it to npm shortly.