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

nestjs-injection-token-resolver

v1.0.2

Published

A tiny utility to standardize the injection token recovery among NestJS libraries.

Downloads

217

Readme

nestjs-injection-token-resolver

npm version npm downloads

A tiny utility to standardize the injection token recovery among NestJS libraries.

Usage

npm install nestjs-injection-token-resolver

When you have a injection using some 3rd-party decorator instead of the @Inject() from @nestjs/core, that 3rd-party component (usually a NestJS library) will share with you a another function to resolve the provider's token so that you can use it in a non-class-based approach like the followin snippets:

@Injectable()
export class UsersService {
  constructor(
    @InjectRepository(User)
    private usersRepository: Repository<User>,
  ) {}
  // ...
}
@Injectable()
export class AlbumsService {
  constructor(
    @InjectDataSource('albumsConnection')
    private dataSource: DataSource,

    @InjectEntityManager('albumsConnection')
    private entityManager: EntityManager,
  ) {}
  // ...
}
@Module({
  providers: [
    {
      provide: AlbumsService,
      inject: [getDataSourceToken('albumsConnection')],
      useFactory: (albumsConnection: DataSource) => {
        return new AlbumsService(albumsConnection);
      },
    },
  ],
})
export class AlbumsModule {}
@Module({
  providers: [
    UsersService,
    {
      provide: getRepositoryToken(User),
      useValue: mockRepository,
    },
  ],
})
export class UsersModule {}

Thus, you will need to know about getDataSourceToken and getRepositoryToken instead of just knowing about the @Inject*() decorator.
And this is for every NestJS lib out there that has some sort of @Inject*() decorator.

With nestjs-injection-token-resolver you can forget about those helper functions!
Instead, just do:

@Module({
  providers: [
    {
      provide: AlbumsService,
      inject: [ InjectionTokenFor( InjectDataSource('albumsConnection') ) ],
      useFactory: (albumsConnection: DataSource) => {
        return new AlbumsService(albumsConnection);
      },
    },
  ],
})
export class AlbumsModule {}
@Module({
  providers: [
    UsersService,
    {
      provide: InjectionTokenFor( InjectRepository(User) ),
      useValue: mockRepository,
    },
  ],
})
export class UsersModule {}