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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@nestjs-devkit/dataloader

v0.1.1

Published

Dependency Injection friendly adaptation of dataloaders for NestJS.

Readme

Dataloader

Dependency Injection friendly adaptation of graphql/dataloader for NestJS.

This package internally uses AsyncLocalStorage to provide a clean cache map for each dataloader in each request, but it may have a slight negative impact on the performance.

Installation

npm i @nestjs-devkit/dataloader

Tutorial

Defining DataLoaders

To define a dataloader, we simply extend the abstract DataLoader and implement the resolve() method.

import { DataLoader } from "@nestjs-devkit/dataloader";
// ... more imports

@Injectable()
export class UserIdLoader extends DataLoader<number, User> {
  constructor(@InjectRepository(User) private repo: EntityRepository<User>) {}

  protected async resolve(keys: number[]): Promise<User[]> {
    return this.repo.find({ id: { $in: keys } });
  }
}

Preparing DataLoaders

Before using the dataloaders, we need to firstly provide these dataloaders.

@Module({
  providers: [UserIdLoader],
  exports: [UserIdLoader],
})
export class UsersModule {}

Besides, the DataLoaderModule is also required for them to work.

@Module({
  imports: [DataLoaderModule.forRoot()],
})
export class AppModule {}

Using Dataloaders

Now we can use the dataloaders simply by injecting them into your resolvers.

@Resolver(() => Book)
export class BooksResolver {
  constructor(private userIdLoader: UserIdLoader) {}

  @ResolveField()
  async owner(@Parent() book: Book) {
    return this.userIdLoader.load(book.owner.id);
  }
}

Remember to import the module where the dataloader is defined.

@Module({
  imports: [forwardRef(() => UsersModule)],
})
export class BooksModule {}

Advanced

Cross-Platform

There is a DataLoaderContext used to provide clean cache maps for dataloaders in each request, which need to be applied by a middleware.

By default, a built-in middleware will be used to apply the context for Express. You can disable it and implement your own one for other platforms.

@Module({
  imports: [DataLoaderModule.forRoot({ middleware: false })],
})
export class AppModule implements NestModule {
  configure(consumer: MiddlewareConsumer): void {
    consumer.apply(FastifyDataLoaderModule).forRoutes("(*)");
  }
}

Contributing

Pull requests are always welcome, but please open an issue firstly before major changes. ;]