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

autoexec

v1.0.1

Published

Autoexec, not .bat

Readme

Autoexec(.bat)

No, of course not autoexec.bat, but a small app, that helps you, as developer, to automatically execute commands on file change.

Why one more app?

Yeah, there are some apps, that doing nearly the same, but... only nearly. With every app, I had problems, missing features, much too complicated, etc.. So I started to write my own one. Here it is.

How to use?

Easy! Just install autoexec global: npm install -g autoexec

or local: npm install autoexec

create your config (see below)

and run: autoexec

CLI options:

Usage: autoexec [options]

Options:
   -c, --config    JSON config file  [autoexec.json]
   -p, --path      working directory  [.]
   -v, --version   print version and exit

Config:

Sample config:

{
    "config": [
        {
            "name": "Templates",
            "path": [
                "templates"
            ],
            "files": [
                "**/*.tpl"
            ],
            "exec": "make templates",
            "blocking": true
        },
        {
            "name": "JavaScript",
            "path": [
                "src",
                "foo/bar/"
            ],
            "files": "**/*.js",
            "exec": "make js",
            "blocking": true
        },
        {
            "name": "Images / CSS",
            "path": [
                "css",
                "images"
            ],
            "files": [
                "**/*.scss",
                "**/*.png",
                "**/*.jpg",
                "**/*.gif"
            ],
            "exec": "make images css"
        }
    ]
}

Every array element of "config" has the following possible options:

  • name: This name is displayed in the log and in the notify
  • path: String or array of strings of the directories to be watched, based on the working directory
  • files: String or array of strings which files should be watches, syntax see anymatch
  • ignored (optional): String or array of strings which files should be watches, syntax see anymatch
  • exec: Command to execute
  • blocking (optional): default is false. If the value is true autoexec will only run one of the blocking entries at the same time. E.g. in the above example, if templates is running, javascript wait until templates is done.