Great functionality, but aren't you a teensy weensy bit worried about polluting the npm namespace?! I appreciate that you're prefixing your 'requirify' generated packages with 'requirify-' prefix, but something about this solution seems like it's abusing the npm tooling. At the very least it's forcing people to download (potentially much) larger npm indexes.
Maybe an npm maintainer can comment.
I'm part of the ops team at npm, personally I love the idea of people finding creative uses for the registry. Within the next few months we hope to add better ways to manage collections of packages on npm: Browserify packages, other-front-end packages, grunt packages, etc.
This is a cool proof of concept, and I think would be a great candidate for some of these new features.
if this is currently a hack, it seems like a great candidate for a refactor into a more robust version- what a handy idea! thank you for making this, i will use it whether its a hack or not!