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

es6-dic

v0.0.4

Published

ES6 Dependency Injection Container

Downloads

5

Readme

es6-dic

ES6 Dependency Injection Container

Install

$ npm install es6-dic

Usage

import Container from 'es6-dic';

var c = new Container();

c.register('a', ['b'], b => b + 'a');
c.register('b', () => 'b');

console.log(c.resolve('a')) // 'ba';

API

.register(name, [dependencies,] factory)

Register name with optional dependencies. factory is used to create instance, the arguments are the specified dependencies.

Dependency order is important.

.resolve(name)

Get instance for name.

Notes

"But how can I run this?!"

Well, I use it with browserify & es6ify. It should work with traceur, but afaik module import/export is not compatible with node.

"But I need circular dependencies!!4"

Well, register the container itself as a dependency, and resolve the needed module in runtime!

var c = new Container();

c.register('inject', () => c);

c.register('beep', ['boop'], function(boop) {
  return function() {
    console.log('beep');
    setTimeout(boop, 1000);
  };
});

c.register('boop', ['inject'], inject => {
  var beep;
  return function() {
    beep = beep || inject.resolve('beep');
    console.log('boop');
    setTimeout(beep, 1000);
  };
});

c.resolve('beep')();

"But I need multiple instances, not singletons!"

Well, then don't return instance in the factory!

c.register('Bar', () => {
  // return new Bar();
  // instead of returning an instance, return a constructor!
  return Bar;
});

c.register('foo', ['Bar'], (Bar) => {
  var instance = new Bar();
});

A more complex example:

class Bar {
  constructor(...stuff) {
    this.stuff = stuff;
  }
  foo() {
    console.log(...this.stuff)
  }
}

c.register('Bar', ['a', 'b'], (a, b) => Bar.bind(null, a, b));

c.register('a', () => 1);
c.register('b', () => 2);

c.register('c', ['Bar'], Bar => {
  var b = new Bar(3);
  b.foo();
});

c.resolve('c'); // 1, 2, 3 \o/ yay!

"Tests?!"

Eeerrr, run them with browserify :S, not very node-friendy. If you have a better solution, please create an issue!

License

MIT