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

namespacer

v0.2.0

Published

A simple way to declare and extend namespaces

Downloads

5

Readme

Namespacer

A simple utility for creating namespaces.

Namespacer is mostly meant for the browser, but it also works with AMD and CommonJS modules, although namespaces usually are not necessary in those environments.

Installation

Bower

bower install namespacer

NPM

npm install namespacer

Usage

Using namespaces is a great way for organizing code. In most other languages, this is a built-in feature. With JavaScript, it must be done using objects.

Typical namespacing with JavaScript occurs like this:

//Usually this step can be skipped, as the root namespace would be declared
//once in the beginning
if (typeof RootNamespace == 'undefined') {
    RootNamespace = {};
}

//To add a property on a namespace, you have to check for its existence first
//One disadvantage is you have to repeat this boilerplate for every level 
//of the namespace.
if (!RootNamespace.level1) {
    RootNamespace.level1 = {};
}

//This way is more compact, but still very cumbersome to write
RootNamespace.level1.level2 = (RootNamespace.level1.level2 || {});

With Namespacer, it becomes simplified:

//use Namespacer.createNamespace() once to declare a root namespace
RootNamespace = Namespacer.createNamespace();

//Add or extend namespaces to your heart's content
RootNamespace('mywebapp')('category')('level1')('level2').property = 'blah';

//When you want to retrieve a value, it can be accessible via dot notation
var prop = RootNamespace.mywebapp.category.level1.level2.property;

Each namespace is a function which, when called with a string, will check for that namespace's existence, and return it, or create a new namespace if not found. Since Function extends Object in JavaScript, this is perfectly valid, and can be treated like a regular object. Note that you cannot assign a value to a namespace, but you can always assign to the property of a namespace.

Tips

//You can also use Namespacer() as a shortcut
RootNamespace = Namespacer();

//For function classes, it is recommended to assign it to a separate variable
//for easier access to the prototype.
var MyClass = RootNamespace('mywebapp')('category')('level1')('level2').MyClass = function(){};

MyClass.prototype.myMethod = function () {};

License

ISC