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

simple-js-di

v1.1.1

Published

A pretty simple DI-container for JavaScript

Downloads

59

Readme

Build Status GitHub release (latest by date) GitHub last commit NPM

js-di

This is a pretty simple DI-container for ES6.

Install

$ npm install simple-js-di

A very simple example

import DI from "simple-js-di";
import FooClass from "./classes/FooClass";

let di = new DI();
di.add('foo', FooClass); // add FooClass as service named 'foo'
const foo = di.resolve('foo'); // get an instance of FooClass

One more example

import DI from "simple-js-di";

class Foo
{
    bar = null;
    constructor(bar) {
        this.bar = bar;
    }

    getGreeting() {
        return this.bar.greeting + ', ' + this.bar.name + '!';
    }
}

class Bar
{
    name = null;
    greeting = null;
    constructor(greeting, name) {
        this.greeting = greeting;
        this.name = name;
    }
}

let di = new DI();
di.add("foo", Foo, [":bar"]);
di.add("bar", Bar, ["Hello", "@name"]);
di.addParameters({
    'name': 'World',
});
const foo = di.resolve("foo");

console.log(foo.getGreeting()); // Hello, World!

For more examples see https://github.com/pilov-pa/js-di/tree/master/examples

Api

Using method add(name, value, dependencies, shared)

Adds new dependency to the container.

Example
di.add("someService", SomeServiceClass, [":anotherService", "@someParameter", 123], true);

or

di.add({
    name: "someService", 
    class: SomeServiceClass, 
    args: [":anotherService", "@someParameter", 123], 
    shared: true,
    tags: ["tag1", "tag2"],
});

Method add() has 5 arguments:

Argument name

This is an alias of the dependency that you should use to resolve it.

Argument className

This argument can be a class or a value. If it is a class then resolving returns the result of calls the class constructor.

Argument args

This argument is array of service dependencies should be pass to service constructor. All dependencies should be registered in the di-container. If dependency name has prefix @ then dependency is an another service. If dependency name has prefix : then dependency is a parameter. Otherwise, the dependency is the passed value as is. Default the empty array.

Argument shared

If this argument is false, each resolving will return a new instance of the class. If this argument is true, only the first resolving will create a new instance, the next calls will use the alredy created instance. Default true.

Argument tags

Tags list. See getByTag()

Using method resolve(name)

Resolving the dependency by the name. All subdependencies will be resolved automatically if necessary.

Method has only one argument: name.

Using method getByTag(tag)

Get all services tagged by tag