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

@einenlum/jic

v0.0.5

Published

Ridiculously simple Dependency Injection Container for NodeJS

Downloads

13

Readme

jic

Ridiculously simple Dependency Injection Container for NodeJS.

Why a DIC?

To improve general code quality thanks to inversion of control, and to avoid using things like proxyquire in your tests.

Why jic?

This is a very simple DIC you can use for small projects, if you don't need much more advanced tools like electrolyte, awilix, or inversifyJS.

No Typescript, no automatic loading. Just a tiny tool to help you build your composition root.

Requirements

Node version >= 8.

Install

npm add --save @einenlum/jic or yarn add @einenlum/jic

Usage

To register services and dependencies: container.register(arrayOfServices, rootDirectory);

To get a service: container.get(idOfTheService);

Example:

const container = require('@einenlum/jic');

container.register([
  {id: 'request', path: 'request'},
  {id: 'curryWurst': path: './curryWurst', dependencies: ['sausage', 'ketchup', 'curry']},
  {id: 'ketchup', path: './ketchup'},
  {id: 'curry', path: './curry', dependencies: ['request']},
  {id: 'sausage', path: './sausage'}
], __dirname) // the path that will be used as root for the internal services

// To fetch the service you want (will always return a singleton):
container.get('curryWurst');
container.get('request');

All internal services must be written as functions with dependencies as parameters.

Examples:

// ./curryWurst.js
const curryWurst = function(sausage, ketchup, curry) {
  return {
    // ...
  };
};

module.exports = curryWurst;
// ./ketchup.js
const ketchup = function() {
  return {
    // ...
  };
};

module.exports = ketchup;

License

MIT License.