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

@routegraph/watcher

v1.0.1

Published

Chokidar-based file watcher that hot-reloads route files into a running RouteGraph.

Readme

@routegraph/watcher

Hot reload for RouteGraph in development — watches your routes/ directory and calls graph.reload() when a route file is added, changed, or removed.

Installation

pnpm add -D @routegraph/watcher

RouteWatcher

class RouteWatcher extends EventEmitter {
  constructor(graph: RouteGraph, options?: WatcherOptions)

  start(): void
  stop(): void
  get isWatching(): boolean

  on(event: 'route:added', cb: (node: RouteNode) => void): this
  on(event: 'route:removed', cb: (node: RouteNode) => void): this
  on(event: 'route:changed', cb: (node: RouteNode) => void): this
  on(event: 'reloaded', cb: (diff: RouteDiff) => void): this
  on(event: 'error', cb: (err: Error) => void): this
}

WatcherOptions

interface WatcherOptions {
  debounceMs?: number   // default: 100 — per-file debounce, prevents duplicate reloads on rapid saves
  ignored?: string[]    // extra chokidar ignore patterns, added to the built-in ones
}

Built-in ignore patterns (always applied, regardless of ignored): **/node_modules/**, **/dist/**, **/_*.

Events

| Event | Payload | Fires when | |---|---|---| | route:added | RouteNode | A new <Method>.ts file appears | | route:changed | RouteNode | An existing <Method>.ts file is modified | | route:removed | RouteNode | A <Method>.ts file is deleted | | reloaded | RouteDiff ({ added, removed, changed }, each RouteNode[]) | After every successful graph.reload() triggered by the above | | error | Error | chokidar itself errors, or graph.reload() throws |

Usage

import { RouteGraph } from '@routegraph/core'
import { RouteWatcher } from '@routegraph/watcher'
import { createExpressRouter } from '@routegraph/express'

const graph = new RouteGraph({ routesDir: './routes' })
await graph.load()

if (process.env.NODE_ENV === 'development') {
  const watcher = new RouteWatcher(graph, { debounceMs: 150 })
  watcher.on('reloaded', (diff) => {
    console.log(`hot reload: +${diff.added.length} ~${diff.changed.length} -${diff.removed.length}`)
  })
  watcher.on('error', (err) => console.error('[watcher]', err))
  watcher.start()

  process.on('SIGINT', () => {
    watcher.stop()
    process.exit(0)
  })
}

app.use('/api', createExpressRouter(graph))

Only edits to files matching the <Method>.ts route naming convention trigger a reload — editing a shared helper (e.g. _shared/db.ts) that a route imports does not itself trigger one, since only the route file's own dynamic import is cache-busted on reload.

Why chokidar

Native fs.watch fires multiple events per save on macOS, doesn't reliably report creation/deletion across platforms, and hits inotify limits on Linux for large trees. chokidar is battle-tested across all three platforms and handles atomic saves and editor backup files gracefully — see DECISIONS.md for the full reasoning. It's the only intentionally-added runtime dependency in this package besides picocolors (used only for the terminal log lines this package prints on its own — reload done (+1 ~0 -0) style messages).