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-pilot

v0.2.3

Published

Interactive CLI for generating NestJS projects with Hexagonal, DDD, or Modular architecture

Downloads

11

Readme

cli/

The cli npm workspace package. This is the user-facing binary (nest-pilot) and the composer engine that powers project generation.

Currently supports:

  • Hexagonal Architecture

What belongs here

  • src/commands/ — Commander command definitions. One file per top-level CLI command (create, and future commands).
  • src/prompts/ — Clack interactive prompt flows. One file per command that requires user input.
  • src/composer/ — The template composer engine (see its own README).
  • src/utils/ — Pure utility functions with no side effects. No I/O, no framework imports.
  • __mocks__/ — Manual Jest mocks for ESM-only runtime dependencies (see ADR-002).

What is forbidden here

  • NestJS imports of any kind — this is a build tool, not an application.
  • Business logic — the CLI is only responsible for collecting user input and invoking the composer.
  • Direct filesystem writes outside of composer/renderFiles.ts.
  • Architecture-specific knowledge in commands or prompts — that belongs in the composer and the templates.

Entry Point

cli/
├── src/index.ts        ← Binary shebang + Commander root program
└── dist/index.js       ← Compiled output (generated by `npm run build`)

Dev Scripts

npm run build     # Compile TypeScript → dist/
npm run dev       # Run from source via tsx (no compile step)
npm run test      # Jest test suite