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

namespaces-js

v1.2.0

Published

Angular-flavored DI container.

Downloads

29

Readme

namespaces

Universal registry

Angular-flavored DI container.

npm version Build Status Coverage Status

API

You can find API here

Install


    $ npm install --save namespaces-js

Motivation

We all love testable and modular code. In most cases it means that every piece of you system depends on other pieces and these dependencies should be injected if we want to make our system testable and flexible. But wiring everything up might be a very tedious task with creating multiple instances, passing them into others and then, once requirements or designed changed, finding, replacing, updating and etc... So, that's why namespaces package was created - to solve this issue. It allows you organize your system parts and easily define their dependencies by creating an application container with namespaces.

Its design is inspired by Angular v1 DI, therefore most of the concepts might be familiar for those of you who are familiar with Angular v1, but some are new.

Usage

Just as a container

Stores values


var Container = require('namespaces-js');
var container = new Container();

container.const('foo', 'bar');

const foo = container.resolve('foo');

console.log(foo); // -> 'bar'

Creates singletons


var Container = require('namespaces-js');
var container = new Container();

container.factory('foo', () => {
    return { do: => 'bar' };
});

const foo1 = container.resolve('foo');
const foo2 = container.resolve('foo');

console.log(foo1 === foo2); // -> true

As a container with dependencies

Resolves dependencies by module name


var Container = require('namespaces-js');
var container = new Container();

container.factory('foo', () => 'bar');
container.factory('qaz', ['foo'], (foo) => `${foo}-fighter`);

const qaz = container.resolve('qaz');

console.log(qaz); // 'bar-fighter';

Resolves dependencies by custom resolver


var Container = require('namespaces-js');
var container = new Container();

container.factory('foo', () => 'bar');
container.factory('qaz', [
    'foo',
    function customResolver() {
        return 'wsx';
    }
], (foo, something) => {
    return `${foo}-${something}`;
});

const qaz = container.resolve('qaz');

console.log(qaz); // 'bar-wsx';

Creates nested containers with namespaces


    var Container = require('namespaces-js');
    var container = new Container();

    container.value('foo', 'bar');;
    container.namespace('my-namespace').value('foo', 'qaz');
    container.namespace('my-namespace/sub-namespace-1').value('foo', 'qaz');

    const foo = container.resolve('foo');
    const foo2 = container.resolve('my-namespace/foo');
    const foo3 = container.resolve('my-namespace/sub-namespace/foo');

    console.log(foo === foo2); // false


    container.namespace('my-namespace').namespace('sub-namespace-2').factory('foobar', [
        'foo',
        'my-namespace-1/foo'
    ], (foo, foo2) => {
        return `${foo} !== ${foo2}`;
    });

    const foobar = container.resolve('my-namespace/sub-namespace-2/foobar');

    console.log(foobar); // 'bar !== qaz';

Namespace Helper

It comes with a handy utility function that converts a given namespace tree into function tree. Each function-node of the tree recieves a module name and returns a full path of it.


    var namespaces = Container.map({
        a: 'b',
        c: ['d', 'e', { f: ['g', 'h'] }]
    });

    var container = new Container();

    container.namespace(namespaces.a()).value('foo', 'bar');
    container.namespace(namespaces.b()).factory('foo', () => 'bar');
    container.namespace(namespaces.c()).factory('foo', () => 'bar');
    container.namespace(namespaces.c.f.g()).value('foo', 'bar');

    container.resolve(namespaces.a('foo'));
    container.resolve(namespaces.c.f.g('foo'));