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

@hazejs/devtools

v1.1.0

Published

Devtools for hazejs on top of devframe: app overview, module and route inspector, dev dashboard and terminals in one hub

Readme

@hazejs/devtools

DevTools for hazejs, built on devframe. Experimental.

The module graph panel

  • Panels at /__devtools/: overview, module graph (events, listeners, jobs, schedules and shared middleware between modules, plus what happened at runtime), routes, request waterfalls with N+1 hints, AI calls and a prompt playground, scheduled tasks and queues, container and events, the OpenAPI docs, the /__haze dashboard and terminals.
  • MCP at /__devtools/__mcp: the same information for coding agents.
  • Static report: haze devtools:report bakes the app structure into a static site.
  • Vite DevTools: in full-stack projects with devtools: true in vite.config.ts, the panels show up inside Vite DevTools.

Install

pnpm add -D @hazejs/devtools

haze dev (and the haze() Vite plugin in full-stack projects) picks it up automatically and prints the URL:

  ➜  Local:    http://localhost:3000/
  ➜  DevTools: http://localhost:3000/__devtools/

The first time a browser connects, enter the one-time code printed in the terminal (or open the printed link).

Connect Claude Code to the MCP endpoint:

claude mcp add --transport http hazejs http://localhost:3000/__devtools/__mcp --header "Origin: http://localhost:3000"

Options

// haze.config.ts
import { defineHazeConfig } from '@hazejs/vite'

export default defineHazeConfig({
  devtools: {
    // base: '/__devtools/',
    // auth: true,       // one-time code on first connect
    // terminals: true,  // terminal panel
    // embedded: true,   // full-stack: floating dock in the frontend
    // mcp: true,        // MCP endpoint for coding agents
  },
  // devtools: false,    // turn it off
})

Part of hazejs — see the DevTools guide.

License

MIT