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

@sbailleul/types_ioc

v1.2.11

Published

Language : Typescript 3+

Readme

Lightweight inversion of control container

Prerequisites

Language : Typescript 3+

In tsconfig.json

{
    "experimentalDecorators": true
}

Installation

    npm i @sbailleul/types_ioc

Usage

Dependency handling

You can't use interface for dependency injection cause interfaces are not compiled in javascript. To solve this limitation use full abstract class and implement these in concrete classes :

export abstract class BaseApplicationRepository{
    abstract getAll(query: Query): Promise<{ count: number; rows: IApplicationModel[] }>
    abstract delete(id: number): Promise<number>;
    abstract getOne(id: any): Promise<IApplicationModel | null>;
}

@Injectable
export class SequelizeApplicationRepository implements BaseApplicationRepository{

    async delete(id: number): Promise<number> {
       return SequelizeApplicationModel.destroy({where: {id}});
    }

    async getAll(query: Query): Promise<{ count: number, rows: IApplicationModel[] }> {
        return  SequelizeApplicationModel.findAndCountAll({offset: query.offset, limit: query.limit});
    }

    async getOne(id: any): Promise<IApplicationModel | null> {
        return  SequelizeApplicationModel.findByPk(id);
    }
}

Decorators

Injectable

@Injectable decorator indicate than your class is injectable in other classes, this decorator is mandatory

InjectionTarget

@InjectionTarget decorator indicate than your class will be target for injection, this decorator is mandatory

InjectedProperty

@InjectedProperty decorator indicate than your class property will be injected by ioc, specify base class name in parameter of decorator, for example:

@InjectionTarget
export class ApplicationService  extends BaseService{

    @InjectedProperty(BaseApplicationRepository)
    protected readonly _repository: BaseApplicationRepository;
}

Add injection tags to ioc

WARNING : If you bind provider which has not @Injectable decorator the CoreContainer will throw critical exception.
Tags are usefull to specify which provider select in case of injection conflict :

    CoreContainer.addInjectionTags('sequelize');
    CoreContainer.bind(BaseApplicationRepository, {class: MongooseApplicationRepository, tags: 'mongoose' });
    CoreContainer.bind(BaseApplicationRepository, {class: SequelizeApplicationRepository, tags: 'sequelize');

In this case for BaseApplicationRepository provider container will select SequelizeApplicationRepository class.

Resolve registered dependencies

CoreContainer.resolve();