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

autowatch

v0.1.1

Published

Automatically restart a node process if one of its files changes

Readme


Autowatch

A dead simple, zero configuration watch tool for Node.js applications.

Installation

$ npm i -g autowatch

Usage

$ autowatch <args...>

Where args... are arguments passed directly to node. Autowatch has no flags or arguments itself.

How does it work?

Autowatch streams all imported modules to the parent Autowatch process for monitoring by injecting itself into require.extensions table handlers.

From there, it uses file watchers provided by Node to handle "rebooting" the process.

By moving module registrations into the parent process, the child process and crash or exit whenever it wants, still allowing the developer to re-run it just by changing a file. This further reduces the feedback loop required to fix typos, syntax errors, etc.

License

Released under the MIT license.