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

@wisemen/nestjs-provider-explorer

v0.1.2

Published

Shared provider discovery utilities for NestJS packages.

Readme

@wisemen/nestjs-provider-explorer

Shared provider discovery utilities for NestJS packages.

This package provides:

  • ProviderExplorerModule to register the explorer with Nest
  • ProviderExplorer to enumerate discovered providers lazily
  • NestjsProvider metadata containing providerClass, providerInstance, and the underlying Nest instanceWrapper

Installation

pnpm add @wisemen/nestjs-provider-explorer

Peer dependencies

pnpm add @nestjs/common @nestjs/core

Register The Module

Import ProviderExplorerModule into the module that needs provider discovery. It wraps Nest's DiscoveryModule, so no extra discovery setup is required.

import { Module } from '@nestjs/common'
import { ProviderExplorerModule } from '@wisemen/nestjs-provider-explorer'
import { ProviderRegistry } from './provider.registry.js'

@Module({
  imports: [ProviderExplorerModule],
  providers: [ProviderRegistry]
})
export class ProviderRegistryModule {}

Explore Providers

Inject ProviderExplorer, then iterate over providers to inspect the discovered classes and instances.

import { Injectable, OnApplicationBootstrap } from '@nestjs/common'
import { ProviderExplorer } from '@wisemen/nestjs-provider-explorer'

@Injectable()
export class ProviderRegistry implements OnApplicationBootstrap {
  constructor (
    private readonly providerExplorer: ProviderExplorer
  ) {}

  onApplicationBootstrap (): void {
    for (const provider of this.providerExplorer.providers) {
      console.info(provider.providerClass.name)
    }
  }
}

Each NestjsProvider exposes:

  • providerClass: the discovered provider metatype
  • providerInstance: the instantiated provider object
  • instanceWrapper: Nest's internal InstanceWrapper, useful when you need to resolve transient or request-scoped providers manually

Filter Providers

The explorer returns all discovered class-based providers. Consumers are expected to filter them with their own decorators or metadata checks.

import { Injectable } from '@nestjs/common'
import { ProviderExplorer } from '@wisemen/nestjs-provider-explorer'
import { isTypesenseCollector } from './typesense-collector.decorator.js'

@Injectable()
export class TypesenseCollectors {
  constructor (
    private readonly providerExplorer: ProviderExplorer
  ) {}

  collect (): void {
    for (const provider of this.providerExplorer.providers) {
      if (!isTypesenseCollector(provider.providerClass)) {
        continue
      }

      provider.providerInstance
    }
  }
}

Scoped Providers

For singleton providers, use providerInstance directly. For transient or request-scoped providers, inspect instanceWrapper and resolve through ModuleRef when needed. This is the pattern used by packages that must defer instantiation until runtime.