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

angular2-di-helper

v0.0.28

Published

An implementation of the dependency injection helpers at Angular2 (2.0.0 compatible).

Downloads

32

Readme

angular2-di-helper

An implementation of the dependency injection helpers at Angular2 (2.0.0 compatible).

Installation

First you need to install the npm module:

npm install angular2-di-helper --save

Use

In general, you don't need configure the providers at the main application module. You have to configure your providers at the main application module only if you use the Singleton annotation.

Use case #1

So, we should integrate the DI module at first.

import {DIModule} from 'angular2-di-helper';

@NgModule({
    imports: [
        DIModule,
        ...
    ],
    providers: [Action],      // Put here your Action if you use the Singleton annotation
    ...
})
export class ApplicationModule {
}

Create the Action as a singleton instance via the factory using @Singleton decorator.

import {Singleton} from 'angular2-di-helper';

@Singleton()
@Injectable()
export class Action {

    constructor(...) {
    }
}

Create the Action2 instance every time as a new instance via the factory.

@Injectable()
export class Action2 {

    constructor(...) {
    }
}
@Injectable()
export class ActionFactory {

    constructor(@Inject(ServiceLocator) private serviceLocator:IServiceLocator) {
    }

    public createAction<TAction>(ctor:{new (...type:Type<any>[]):TAction}):TAction {
        return this.serviceLocator.getService<TAction>(ctor);
    }
}

Use case #2

You have to configure your providers at the main application module using service locator only if you have a "special configuration" of providers, for example:

class DiClass {
    constructor() {
    }
}

class DiClass1 extends DiClass {
    constructor() {
        super();
    }

    methodOfClass1():void {
        console.log('Method is called');
    }
}

@NgModule({
    imports: [DIModule, ...],
    providers: []               // Empty providers section at the main application module!
})
export class ApplicationModule {
    constructor(@Inject(ServiceLocator) serviceLocator:IServiceLocator) {
        serviceLocator.configure([{     // Configures only the service locator!
            provide: DiClass,
            useClass: DiClass1
        }]);
    }
}

@Component(...)
export class AppComponent {
    constructor(@Inject(ServiceLocator) private serviceLocator:IServiceLocator) {
        const instance1:DiClass1 = this.serviceLocator.getService(DiClass);
        const instance2:DiClass1 = this.serviceLocator.getService(DiClass);
    
        instance1.methodOfClass1();                             // Console output: "Method is called"
        instance2.methodOfClass1();                             // Console output: "Method is called"
        console.log(instance1 === instance2);                   // Console output: "false"
    }

Publish

npm run deploy

License

Licensed under MIT.