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

@laphilosophia/steady-watch

v1.0.1

Published

Intelligent file watcher with content hashing and debouncing. No more ghost rebuilds.

Readme

🔭 Steady Watch

Intelligent file watcher with content hashing and debouncing. No more ghost rebuilds.

npm version License: MIT

The Problem

Standard file watchers trigger on every save, including:

  • Editor auto-saves that don't change content
  • IDE temp file operations
  • Multiple rapid saves

This leads to unnecessary rebuilds, wasted CPU cycles, and noisy logs.

The Solution

Steady Watch uses MD5 content hashing to detect actual changes. If the file content hasn't changed, no rebuild is triggered. Period.

Installation

npm install -g @laphilosophia/steady-watch

Usage

steady-watch "src/**/*.ts" -c "npm run build"

Or use the short alias:

sw "src/**/*.ts" -c "npm run build"

Options

| Option | Description | Default | |--------|-------------|---------| | -c, --cmd <command> | Command to execute on change | required | | -d, --delay <ms> | Debounce delay in milliseconds | 300 | | -v, --verbose | Show hash calculations and file indexing | false |

Examples

# TypeScript build
sw "src/**/*.ts" -c "npm run build"

# Run tests on change
sw "src/**/*.{ts,tsx}" -c "npm test" -d 500

# Verbose mode to see what's happening
sw "lib/**/*.js" -c "node build.js" -v

Features

  • 🎯 Content Hashing — Only triggers when file content actually changes
  • ⏱️ Debouncing — Batches rapid changes into single rebuilds
  • 🚀 Process Management — Won't start new build while previous is running
  • 🚫 Smart Ignores — Auto-ignores node_modules, .git, dist, build
  • 🎨 Pretty Output — Color-coded, timestamped logs

Output Example

🔭 Steady Watch Initialized
   Pattern: src/**/*.ts
   Command: npm run build
   Delay:   300ms

👁️  Watcher ready. Monitoring for changes...
   Tracking 12 file(s)

[9:53:26 PM] ⚡ Change detected: index.ts
[9:53:26 PM] 🚀 Triggering: npm run build
[9:53:28 PM] ✔ Done in 2.14s
────────────────────────────────────────

License

MIT © Erdem Arslan