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

nodejs-ioc-container

v2.0.0

Published

NodeJs Ioc Container & Lazy Dependencies Loading

Downloads

12

Readme

nodejs-ioc-container

This project will be supported:

  • Ioc Container
  • Lazy Dependencies loading

Usage

Create a Container

A Container is a single unit of dependency handling. It registers dependencies and resolves them for dependency consumers.

var container = require('nodejs-ioc-container').getContainer();

container.register(...
container.resolve(...
container.get(...
container.destroy();

Register a Dependency

container.register('connection', connection);

connection is either an object or a function that will return a connection object. You cannot register functions that will depend on other dependencies - this you can do with v1.0.0 - https://github.com/dexter0201/nodejs-ioc-container/releases/tag/v1.0.0

Consume dependencies

get

Use get when you need to check if the dependency is registered, because get returns immediately.

container.get('connection', function(connection) {
    if (!connection) {
  
    } else {
  
    }
});

In the above example, if the get is called before connection is registered, you will get null.

resolve

If you have a function that needs a connection, use

container.resolve('connection', function(connection) {/*use connection*/});

resolve also supports the "Array notation":

container.resolve(['connection', function (connection){/*use connection*/});

and, of course, the "dependable notation":

container.resolve(function(connection) {/*use connection*/});

tldr: if resolve gets a function as a first parameter, it will stringify/parse it to read the names of dependables you need.

Chain dependency providers

You can register functions that will depend on other dependencies and chain dependency providers. For example, if you cannot provide a database without obtaining a configuration first, you register your database provider in the following manner:

container.register('database',function (configuration) {
  //use the configuration to produce your database connection
  var database = createDatabase(configuration);
  //and finally
  return database;
});