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

@angelitosystems/nest-devtools-cli

v2.0.1

Published

DevTools server, dashboard hosting and CLI for NestJS DevTools.

Readme

@angelitosystems/nest-devtools-cli

CLI, servidor local y dashboard para NestJS DevTools.

Este paquete incluye el ejecutable nest-devtools, el servidor HTTP/WebSocket y el dashboard estatico embebido. Se instala en la maquina de desarrollo, no dentro de cada aplicacion NestJS.

Instalacion

Uso puntual con npx:

npx @angelitosystems/nest-devtools-cli

Instalacion global:

npm install --global @angelitosystems/nest-devtools-cli
bun add --global @angelitosystems/nest-devtools-cli

Comandos

nest-devtools                  Inicia el servidor y el dashboard
nest-devtools start            Inicia el servidor con opciones de red
nest-devtools status           Comprueba el endpoint HTTP
nest-devtools projects         Lista proyectos conocidos
nest-devtools logs             Muestra eventos de log recientes
nest-devtools doctor           Diagnostica runtime, HTTP y WebSocket
nest-devtools init             Conecta automaticamente el SDK en main.ts
nest-devtools --version        Muestra la version instalada
nest-devtools --help           Muestra la ayuda

Ejemplos:

nest-devtools start --port 4319 --ws-port 4320 --host localhost
nest-devtools status --port 4319
nest-devtools doctor --port 4319 --ws-port 4320
nest-devtools init

nest-devtools init modifica src/main.ts o main.ts, anade el import de NestDevTools y coloca NestDevTools.init(app) despues de NestFactory.create(...). Es idempotente.

Puertos

| Puerto | Uso | |---:|---| | 4317 | Dashboard HTTP y endpoint /health | | 4318 | Conexiones WebSocket del SDK |

Abre el dashboard en http://localhost:4317. Si cambias el puerto WebSocket, configura el SDK con NEST_DEVTOOLS_URL o con la opcion server de NestDevTools.init().

API programatica

El paquete tambien exporta DevToolsServer, DashboardStore, CLIRenderer, parseArgs, openInEditor y openTerminal para integraciones internas y herramientas de desarrollo.

import { DevToolsServer } from '@angelitosystems/nest-devtools-cli';

const server = new DevToolsServer({
  httpPort: 4317,
  wsPort: 4318,
  host: 'localhost',
});

await server.start();

Desarrollo

bun run --cwd apps/dashboard build
bun run scripts/prepare-publish.ts
bun run --cwd packages/cli build
bun test packages/cli

El dashboard debe copiarse a packages/cli/public antes de publicar. El proceso de release del monorepo realiza este paso automaticamente.

Licencia

MIT. Consulta docs/cli.md para el uso detallado.