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

@hazeljs/inspector

v1.0.5

Published

Framework-aware runtime inspector for HazelJS - metadata explorer and DevTools UI

Readme

@hazeljs/inspector

Framework-aware runtime inspector for HazelJS. Explore metadata, routes, modules, providers, cron jobs, queues, WebSocket gateways, and more at runtime.

Features

  • Metadata explorer – Inspect what HazelJS has registered (routes, modules, providers, decorators)
  • Package-specific plugins – Optional support for @hazeljs/cron, @hazeljs/queue, @hazeljs/websocket
  • DevTools UI – Overview dashboard, search, filters, detail views, runtime stats
  • JSON API – Consume inspector data programmatically

Installation

npm install @hazeljs/inspector @hazeljs/core

Quick Start

Add InspectorModule.forRoot() to your app:

import { HazelModule } from '@hazeljs/core';
import { InspectorModule } from '@hazeljs/inspector';

@HazelModule({
  imports: [
    InspectorModule.forRoot({
      inspectorBasePath: '/__hazel',
      developmentOnly: true,
      exposeUi: true,
    }),
    // ... other modules
  ],
})
export class AppModule {}

Then run your app and open:

  • http://localhost:3000/__hazel – DevTools UI
  • http://localhost:3000/__hazel/inspect – Full snapshot (JSON)
  • http://localhost:3000/__hazel/routes – Routes only
  • http://localhost:3000/__hazel/modules – Modules only
  • http://localhost:3000/__hazel/providers – Providers only
  • http://localhost:3000/__hazel/jobs – Cron jobs (if @hazeljs/cron is installed)
  • http://localhost:3000/__hazel/queues – Queue processors (if @hazeljs/queue is installed)
  • http://localhost:3000/__hazel/websocket – WebSocket gateways (if @hazeljs/websocket is installed)
  • http://localhost:3000/__hazel/stats – Runtime stats (memory, uptime)

Configuration

| Option | Default | Description | | ----------------------- | ------------ | ------------------------------------------- | | enableInspector | true | Enable the inspector | | inspectorBasePath | '/__hazel' | Base path for all inspector endpoints | | exposeUi | true | Serve the DevTools UI at the base path | | exposeJson | true | Expose JSON endpoints | | developmentOnly | true | Disable in production (NODE_ENV=production) | | maxSnapshotCacheAgeMs | 5000 | Cache snapshot for 5 seconds |

Security

  • Dev-only by default – When developmentOnly: true and NODE_ENV=production, the inspector is disabled
  • Sensitive data – Metadata is redacted for known keys (password, secret, token, etc.)
  • Explicit opt-in – Set developmentOnly: false and enableInspector: true to use in production (not recommended)

Custom Plugins

Register your own inspector plugin:

import { HazelInspectorRegistry, type HazelInspectorPlugin } from '@hazeljs/inspector';

const myPlugin: HazelInspectorPlugin = {
  name: 'my-plugin',
  supports: (ctx) => true,
  inspect: async (ctx) => [{ id: 'custom:1', kind: 'route', packageName: '@my/package' /* ... */ }],
};

// Register during bootstrap (e.g. in a provider that runs early)
registry.register(myPlugin);

Architecture

  • Registry – Pluggable inspector plugins
  • Core plugin – Routes, modules, providers, decorators (uses collectControllersFromModule, collectModulesFromModule from @hazeljs/core)
  • Optional plugins – Cron, queue, websocket (loaded when packages are installed)
  • Service – Aggregates results, caches snapshot
  • Transport – HTTP handler for /__hazel/*

License

Apache-2.0