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

@nexusdi/cli

v0.4.0-rc.1

Published

Audit and visualize your application architecture from the terminal.

Downloads

504

Readme

@nexusdi/cli

npm license

Audit and visualize your application architecture from the terminal.

As dependency graphs grow, it becomes difficult to detect circular dependencies, unintended couplings, or missing bindings without running the entire application. @nexusdi/cli solves this by extracting your dependency tree into a visual or structured format without instantiating your providers.

npx nexusdi graph src/app.module.ts#AppModule -o graph.svg

Key Features

The CLI imports your entry file and analyzes the graph without instantiating any provider. Keep the Nexus.create call that starts your app out of that file, because its top-level code runs. It supports multiple output formats including Mermaid, DOT, JSON, SVG, and PNG. The tool returns exit code 1 on invalid graphs, allowing you to block broken wiring in CI/CD pipelines.

Options

The CLI provides several flags to control the analysis and output.

| Flag | Purpose | Example | | :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------- | | -f, --format | Choose output format (mermaid, dot, json, svg, png). Default: from --out's extension, else mermaid. SVG needs @viz-js/viz, and PNG also needs @resvg/resvg-js. | -f svg | | -o, --out | Save the output to a file | -o graph.svg | | --view | Switch between providers (default) or modules view | --view modules | | --load | Simulate loading a module at runtime. Repeatable. | --load src/feature.ts#Feature | | --plugins | Pass the exported array of plugins your app gives Nexus.create | --plugins src/plugins.ts#plugins |

Installation

0.4 is a release candidate on the npm next tag. Install every @nexusdi package from next so their versions match. Without @next, npm installs core 0.3 and stops with a peer conflict.

npm install -D @nexusdi/cli@next @nexusdi/devtools@next @nexusdi/core@next

Usage

You can target specific modules to generate diagrams or export data.

npx nexusdi graph src/app.module.ts#AppModule
npx nexusdi graph src/app.module.ts#AppModule -o graph.svg
npx nexusdi graph src/app.module.ts#AppModule --view modules
npx nexusdi graph src/app.module.ts#AppModule -f json -o graph.json

A .ts entry on Node before 22.18 needs tsx installed. Every command exits 1 when the graph is invalid. Add the last one to your CI pipeline to prevent broken wiring from being merged.

Documentation

License

MIT