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

export-dir

v0.1.2

Published

Tool to require all files in a single directory in Node.JS

Downloads

57

Readme

export-dir

Node.JS module which allows you to require all of the files in an entire directory with a single call to require.

Rationale

The default behavior of the Node.JS require function when you give it a directory path, for example require('./mymodules'), is to look for an index.js file in the relative directory mymodules.

Example

That is, it will load ./mymodules/index.js This is useful, but sometimes you kind of wish that it imported all of the scripts in that directory instead.

Suppose I have a directory structure like so:

-mymodules      // directory
  * first.js    // contains -- module.exports = { name: 'first' }
  * second.js   // contains -- module.exports = { name: 'second' }
  - third       // directory
    * index.js  // contains -- module.exports = { name: 'third' }
  - more        // directory
    * fourth.js // contains -- module.exports = { name: }
    * fifth.js

I would like to get the following object back when I call require('./mymodules'):

 {
    first: {
        name: 'first'
    },
    second: {
        name: 'second'
    },
    third: {
        name: 'third'
    },
    more: {
        fourth: {
            name: 'fourth'
        },
        fifth: {
            name: 'fifth'
        }
    }
 }

Usage

You should include export-dir as a dependency in your package.json file, you may do so by runnning:

npm install export-dir --save

In order to export an entire directory structure like in the example you need to place an index.js file into the desired directory which contains the following lines:

var exportDir = require('export-dir');
module.exports = exportDir(__dirname);

In the above example you would need to create an index.js file like this in both the ./mymodules directory and in ./mymodules/more in order to get the exported object shown above.

Testing

This project uses the mocha module for testing. This dependencies is only for development and is not needed for use of export-dir. In order to install the development dependencies and run the tests using npm please run:

npm install -d
npm test