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

modular

v0.0.4

Published

Automatically turn a directory of files into an exported node module structure.

Downloads

70

Readme

Modular

Modular allows simple exportation of a module directory to a node module structure. Individual files are only required when the exported object's property is accessed.

Installation

% npm install -g auto-module

Usage

A require("modular") returns a function that takes two optional arguments.

module.exports = require("modular")([src], [options]);

src, if given, should be a string that is a path to a directory to turn into an Modular. If not given, the directory of the file that required Modular will be used.

options, if given, should be an object with one, or more, of the following properties:

  • recursive: Whether or not to recursively turn sub-directories into Modulars also. Default is true.

  • keyFormatter: A function to use to transform a filename into a property key. The default is to camel-case the file name by splitting the base filename (minus any extension) on whitespace or a hyphen, and then title case all words after first. i.e:

    "my-foo-function" => "myFooFunction"
    "My-Base-Class" => "MyBaseClass"
    "-my-other-class" => "MyOtherClass"
        
  • excludes: An array of strings, or Regular Expressions, to use to exclude certain files. The exclude pattern will be applied to a file's basename.

Example

Given the following directory structure:

my-module/
    index.js
    foo.js
    foo-bar/
        Baz.js
        buz.js

If the content of my-module/index.js is the following:

module.exports = require("modular")();

Would produce the following module/object structure:

{
    foo: {
        // the exports of my-module/foo.js
    },
    fooBar: {
        Baz: {
            // the exports of my-module/Baz.js
        },
        buz: {
            // the exports of my-module/buz.js
        }
    }
}

But, not really.

The actual property is not resolved (the underlying file required) until it is accessed. So, really, when first required the exported object looks like this:

{
    foo: [Getter],
    fooBar: [Getter]
}

After foo and fooBar are accessed, it would look like this:

{
    foo: {
        // the exports of my-module/foo.js
    },
    fooBar: {
        Baz: [Getter],
        buz: [Getter]
    }
}

And so on.