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

dejected

v1.0.0

Published

Typescript no frills dependency injection

Downloads

5

Readme

dejected

  • Straight forward dependency injection.
  • No need to change existing code, or turn on annotations.
  • Supports multiple lifetime scoping and object disposal.
  • Easy to use fluent interface.

Installation

Install using npm

npm install dejected

Usage

To use dejected in your code simply create containers, register items (classes, factories, instances, or primitive values), and resolve.

At a glance

import { newContainer } from 'dejected';

const rootContainer = newContainer()
            .registerClass("userClient", UserClient)
            .inject("clientUrl")
            .asSingleton()
            .registerClass("userService", UserService)
            .inject("userClient")
            .asSingleton()
            .registerClass("eventBus", EventBus)
            .asTransient();

const childContainer = rootContainer
            .createChild()
            .registerClass("userService", OtherUserService)
            .inject("userClient")
            .asSingleton();

rootContainer.registerValue("clientUrl", "https://a.b.c/1010");

const userService = childContainer.resolve("userService");
const eventBus = childContainer.resolve("eventBus");

childContainer.dispose();
rootContainer.dispose(); 
  

Registering items in a container

The following items can be registered in a container, using a unique token identifier:

  • Constructors
  • Factories (functions that return items)
  • Instances (objects)
  • Values (numbers, strings, or undefined)

Constructors and Factories can be registered with the following scope:

  • Singleton - the constructor or factory will be called only once, and will return the same item on subsequent calls.
  • Transient - the constructor or factory will be called every time a resolve from the container takes place.

Dependencies are injected in the order specified, and are defined using:

  • inject - provide the relevant token and the dependency will be resolved from the container on construction
  • injectValue - provide a primitive value (number or string) which will be used as the dependency
  • defaultArg - use this when a constructor/factory has a default argument (optional)

Lifetime Scopes

The containers support a tree structure of lifetime containers.

  • You can create multiple children from any level of container.
  • Dependencies will be resolved from the current scope or above.
  • Therefore singleton objects will not have dependencies in a child scope.
  • When a container is disposed, any child containers will also be disposed.