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

safe-provide

v2.0.0

Published

A typesafe way to create Angular 2 providers

Downloads

3

Readme

Safe provide

A typesafe way to inject implementations for Typescript interfaces in Angular 2.

Why is this needed?

Angular's allows the user to configure how the injector will instantiate a token. This is commonly used to inject an implementation class when a component requires an interface to be injected. However, Angular does not check that the implementation satisfies the given interface. Consider the following example:

{provide: UserProviderToken, useClass: HttpUserProvider}

Interface information is lost after Typescript compilation. This means that no check is performed that HttpUserProvider implements UserProvider. The error only shows up in integration tests (or at runtime if test coverage is poor).

When using safe-provide's safeProvide function we get a compile-time check that HttpUserProvider implements UserProvider.

safeProvide(UserProviderToken).useClass(HttpUserProvider);

Usage

In the following example we configure angular to inject an instance of the HttpUserProvider class for the UserProvider interface.

  1. Install package.

     $ npm install safe-provide --save
  2. Create a SafeToken for your interface.

     // userProvider.ts
        
     import {SafeToken} from "safe-provide";
        
     export const UserProviderToken = new SafeToken<UserProvider>("UserProvider");
        
  3. Configure a provider using safeProvide.

     // main.ts
        
     import {safeProvide, SafeToken} from "safe-provide";
        
     bootstrap(AppComponent, [
         safeProvide(UserProviderToken).useClass(HttpUserProvider)
     ]);

    The safeProvide function can be used anywhere angular allows provider configuration. Unlike with the Angular provide function, compilation will fail if the HttpUserProvider does not implicitly or explicitly implement UserProvider. We also have the option of providing a value

     safeProvide(UserProviderToken).useValue(new HttpUserProvider())
        

    or a factory function that returns an HttpUserProvider.

     safeProvide(UserProviderToken).useFactory(userProviderFactory)
  4. Inject the UserProvider by passing the SafeToken to @Inject.

     // userComponent.ts
        
     @Component({
         // configuration
     })
     export class UsersComponent {
         constructor(@Inject(UserProviderToken) private userProvider:UserProvider) {
         }
     }