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

namespace-generator

v1.2.1

Published

The namespace NPM will take a starting directory and build out objects and modules that are in a given directory structure.

Downloads

18

Readme

Namespace Generator

Build Status

The namespace NPM will take a starting directory and build out objects and modules that are in a given directory structure. The purpose of this module is so that you can establish a directory for various modules and not have to worry about linking them together. Specifically statically referencing modules in an index.js or something equivalent.

This module can be used both asynchronously or synchronously.

The start path should contain all forward slashes, since the module uses glob.

Aysnc Usage

myModule.js

let namespace = require('solid-namespace');
namespace(path.join(__dirname, '../my-modules'))
    .then(function(ns){
            //`ns` object is fully loaded with an organized object based off of your file system

            //examples (see tests)
            ns['test-start']; //should.equal('lets get ready to rumble');
            ns.dir1.test1(); //should.equal('i am test1');
            ns.dir1.test2.test2a(); //should.equal('i am test2a');
            ns.dir1.test2.test2b(); //should.equal('i am test2b');
            ns.dir2.testa.testa; //should.equal('i am test a');
            ns.dir2.testb.testb; //should.equal('i am test b');
            ns.dir1.subdir1['test-z']; //should.equal('i am test-z');
        });

Sync Usage

myModule.js

let namespace = require('solid-namespace');
let ns = namespace.sync(path.join(__dirname, '../my-modules'))
//`ns` object is fully loaded with an organized object based off of your file system

//examples (see tests)
ns['test-start']; //should.equal('lets get ready to rumble');
ns.dir1.test1(); //should.equal('i am test1');
ns.dir1.test2.test2a(); //should.equal('i am test2a');
ns.dir1.test2.test2b(); //should.equal('i am test2b');
ns.dir2.testa.testa; //should.equal('i am test a');
ns.dir2.testb.testb; //should.equal('i am test b');
ns.dir1.subdir1['test-z']; //should.equal('i am test-z');

See tests for full example.

Note that any . in the filename after removing the suffix are turned into _. This is becuase otherwise they would result in nested objects. For example this.file.js would be turned into the key this_file.

Options

By default the module takes all .js files and composes and object out of them. You can optionally pass an alternative glob expression, and an optional suffix to remove to create the keys. The globe expression should begin with a forward slash.

e.g.:

services
    some.service.js
    index.js
    email
        send.service.js

Running namespace(path.join(__dirname, 'services'), '/**/*.service.js', '.service.js') would project an object with the keys:

{
    "some" : "",
    "email": {
        "send" : ""
    }
}

Built with love by Solid Digital

Solid is addicted to digital, fanatic about mobile and intrigued by the Internet of things.

At Solid, we create digital products and services that will transform our physical world.

Let's chat @http://solid.ws