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

nest-graph-inspector

v0.2.3

Published

NestJS module graph inspector for discovery and dependency analysis

Downloads

559

Readme

Nest Graph Inspector

Nest Graph Inspector is a NestJS module to generate a runtime dependency graph in Markdown + Mermaid or JSON format from the Nest application container.

The generated graph shows:

  • loaded modules from the root module
  • import relationships between modules
  • providers and controllers in each module
  • dependencies between providers/controllers
  • internal dependencies, external module dependencies, and selected NestJS core dependencies

[!NOTE] Result of markdown can be seen on https://github.com/albasyir/nest-graph-inspector/blob/main/src/graph-output.md

Use Cases

important to see what's actual problem that can be solved with this, we think you have them too!

Impact Analysis

  • narrowing regression test scope to the most relevant modules/providers
  • reducing unnecessary testing for unrelated areas
  • understanding the likely blast radius before making a change

Test Prioritization

  • selecting critical providers/use cases for fast validation
  • understanding dependency chains between providers/controllers
  • prioritizing which flows should be checked first after a change

Architecture Visibility

  • onboarding engineers faster
  • spotting highly coupled modules/providers
  • making refactors safer by visualizing relationships before changes

Installation

npm install nest-graph-inspector

Version Supports

Official support: NestJS 10-11.

[!NOTE] Earlier versions may still work, but are not officially supported. If you still want to install it with an unsupported NestJS version, you can force install it with:

npm install nest-graph-inspector --force

When you test it and work prefectly, raise on issue so i will update support coverage too

Usage

forRoot

Static config.

import { Module } from '@nestjs/common';
import { AppModule } from './app.module';
import { NestGraphInspector } from 'nest-graph-inspector';

@Module({
  imports: [
    NestGraphInspector.forRoot({
      rootModule: AppModule,
      output: {
        file: 'test.md',
      },
    }),
  ],
})
export class RootModule {}

forRootAsync

Factory-based config.

NestGraphInspector.forRootAsync({
  useFactory() {
    return {
      rootModule: AppModule,
      output: {
        file: 'test.md',
      },
    };
  },
}),

Config

rootModule

Graph entry point.

rootModule: AppModule

output.file

Output markdown file name.

output: {
  file: 'test.md'
}

Output

all output will contains

  • module list
  • imports module
  • exports provider
  • providers with dependencies
  • controllers with dependencies

when markdown file as output, it will show depedencies graph

markdown use mermaid, open markdown in place that support mermaid, in VSC you can install plugin

Flow

  1. start from the configured root module
  2. inspect the Nest runtime container
  3. collect module and provider metadata
  4. resolve dependencies
  5. generate output

Notes

  • the graph is generated from the runtime Nest container, not from static source parsing
  • selected NestJS core dependencies can be grouped under NestJS Core Module as Global Module