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

tiny-dependecy-injection

v1.0.3

Published

a simple library for dependency injection in node

Downloads

24

Readme

Tiny-dependecy-injection

a simple library for dependency injection in node

Installation

npm install --save tiny-dependency-injection

Usage: register and get services

// reporitories/UserReporitory.js

export default class UserReporitory {
  /**
   * @param {ExampleService} exampleService
   */
  constructor(exampleService) {
    this._exampleService = exampleService;
  }

  ...
}

You can register this in the container as a service:

import {ContainerBuilder} from 'tiny-dependecy-injection'
import {UserReporitory} from './reporitories/UserReporitory.js'
import {ExampleService} from './services/ExampleService' 

const container = new ContainerBuilder()

container.register('service.example', ExampleService)
container
    .register('reporitories.ures-repository', UserReporitory)
    // For the argument to return an instance of the service, the prefix '@' must be used, 
    // otherwise it will be taken as a string
    .addArgument('@service.example')

And get services from your container

const reporitory = container.get('@reporitories.ures-repository')

You can also configure the scope of the service, by default it is scoped

container
    .register('reporitories.ures-repository', UserReporitory)
    .addArgument('@service.example')
    .asSingleton()

or

container
    .register('reporitories.ures-repository', UserReporitory)
    .addArgument('@service.example')
    .asScoped()

Arguments

any type of arguments can be set

container
    .register('reporitories.ures-repository', UserReporitory)
    .addArgument('string')
    .addArgument(true)
    .addArgument({ environment: 'test' })
    .addArgument('@service.example')
    .addArgument(new ExampleService())

To use environment variables in arguments is done as follows;

container
    .register('reporitories.ures-repository', UserReporitory)
    .addArgument('$env(MY_VARIABLE)')

NOTE: If the variable does not exist, an error will be thrown.

Factories

factories can also be registered

//factories/ServiceFactory.js
import {ExampleService} from './services/ExampleService' 

export default class ServiceFactory {
    static createServise(param) {
        return new ExampleService(param)
    }
}

To register the factories you have to specify the name of the function to be invoked, you can also assign parameters to the factory function

container
    .register('factories.ServiceFactory', ServiceFactory, 'createServise')
    .addArgument('param')

Mentions

For this package I was inspired by Node Dependency Injection