npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

bulk-export

v1.0.1

Published

Requires files in a directory and returns the results as a keyed object

Downloads

3

Readme

bulk-export

Requires files in a directory and returns the results as a keyed object

This was kinda of an experiment in removing boilerplate stuff I was typing over and over again when exposing a "namespace" module

Automagically load sub files and export them thus removing the painful touch index file every time you add something dance...

Update

This turned out to be just a bit too magic so I don't actually use it...

Usage

With a structure such as:

services
    |__ foo.js
    |__ bar.js
    |__ index.js

You would normaly have code like this in index.js

module.exports = {
    foo: require('./foo'),
    bar: require('./bar')
}

So that somewhere else you could just require services and get an object like this:

{
    foo: 'contents of foo',
    bar: 'contents of bar'
}

with this module the contents of index.js is just

module.exports = require('bulk-export');

and you would get the same result

Issues

  1. This is waaaaaay too magical and unless you know what this module does you can not work it out by reading the code.
  2. Only works once, this was an experiment so I haven't bothered to make it a function to break the require cache stuff.
  3. It will probably do crazy stuff with async load and require cache if I was to actually do it as above.