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 🙏

© 2026 – Pkg Stats / Ryan Hefner

small-di

v1.0.0

Published

⭐ REALLY small package for DI injection

Readme

Small DI

NPM Version

Lightweight, zero dependencies, type-safe, without decorators and reflect-metadata.

Installation

Install with npm:

npm i small-di

Usage

First, specify your classes, variables, etc.:

interface IApi {
    fetchData(): void;
}
interface IUserService {
    getUser(): void;
}

class Api implements IApi {
    public fetchData() {
        console.log('fetchData')
    }
}

class UserService implements IUserService {
    constructor(private readonly api: IApi) {}

    public getUser() {
        console.log('getUser')
    }
}

const config = {
    SECRET: 'secret',
} as const

Now, provide them to container. You must specify how your deps should be created and injected:

const di = createContainer<{ // provide some types
    api: IApi,
    userService: IUserService,
    config: typeof config, // manually created types are optional, but recommended
}>({
    api: {
        factory(): IApi {
            return new Api();
        },
        mode: 'singleton', // if not specified, "default" is used
    },
    userService: {
        factory({ api }): IUserService { // factory gets "deps" object
            return new UserService(api);
        },
    },
    config: {
        factory() {
            return config;
        }
    }
})

Get what you need:

const api = di.resolve('api');
api.fetchData();

const userService = di.resolve('userService');
userService.getUser();

const config = di.resolve('config');
console.log(config.SECRET);

...and that's all.

Also, you'll get error if try to resolve missing dependency or face circular dependency:

const di = createContainer<{
    dep1: any,
    dep2: any,
    dep3: any,
}>({
    dep1: { factory({ dep2 }) {} },
    dep2: { factory({ dep3 }) {} },
    dep3: { factory({ dep2 }) {} },
})

di.resolve('dep4') // Error: Dependency "dep4" not found
di.resolve('dep1') // Error: Circular dependency detected: dep1 -> dep2 -> dep3 -> dep2

API

createContainer(spec)

Creates new container. spec provides information, how deps should be handled:

  • spec.factory(deps) - creation method for dependency
  • spec.mode? - default or singleton. If default will be created every time when requested. If singleton - will be created only once, and then reused.

Requested means using .resolve or by getter deps.depName in factory (handled with Proxy).

container.resolve(name)

Resolves dependency by its name.

License

MIT