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

@valkyr/inverse

v0.18.0

Published

A simple dependency injection container.

Downloads

13

Readme

Inverse

Minimal type safe dependency injection library for TypeScript.

Install

$ npm install @valkyr/inverse

Introduction

Inverse is a small personal dependency injection library used mainly to allow for developing against contracts instead of concrete implementations. It is not meant to be a full blown dependency injection framework, but rather a simple way to allow for swapping out implementations without having to change the code that uses them.

It's unorthodox in that it does not use common pattern of decorator based injection, but allowing for the container to retrieve dependencies in any part of your code base using a class or string identifier (token).

The following documentation will give a brief and simple overview to get your started.

Getting Started

This getting started guide will take you through the basics of using Inverse for dependency injection:

  1. Creating a Dependency

Creating a Dependency

A contract represents the interface in which we develop against. It does not provide any implementation, but rather defines the methods and properties that must be implemented by the concrete implementation.

In our recommended approach we use an abstract class to define the contract, this allows us to use the class as a dependency Token which serves as a guard and contract interface.

Let's start by creating a simple contract for a Logger:

export abstract class Logger {
  abstract log(message: string): void;
}

This contract defines a single method log which takes a string as an argument and does not return anything.

Now that we have a contract we can create a concrete implementation of the Logger:

import { Logger } from "~Logger";

export class ConsoleLogger implements Logger {
  log(message: string): void {
    console.log(message);
  }
}

export class StdLogger implements Logger {
  log(message: string): void {
    process.stdout.write(message);
  }
}

This implementation simply logs the message to the console.

Now that we have a contract and a concrete implementation we can register the concrete implementation with the container:

import { Container, token } from "@valkyr/inverse";

import { ConsoleLogger } from "~ConsoleLogger";
import { Logger } from "~Logger";

const container = new Container([token.transient(Logger, ConsoleLogger)]);

The token.transient method is used to register a concrete implementation with the container. The first argument is the contract Token and interface, the second argument is the concrete implementation.

Inverse uses the concept of optionally providing a default set of implementations when the container is created. When provided the default implementation should be a safe default for your application.

You can register or replace a dependency at any time using the set method:

import { container } from "~Container";
import { Logger } from "~Logger";
import { StdLogger } from "~StdLogger";

container.set(Logger, StdLogger);