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 🙏

© 2024 – Pkg Stats / Ryan Hefner

rerun-script

v0.6.0

Published

Invoke npm scripts upon file changes. Configure via package.json using glob patterns.

Downloads

1,104

Readme

rerun-script

Build Status NPM version NPM downloads LICENSE js-standard-style

Invoke npm scripts upon file changes. Configure via package.json using glob patterns.

$ npm install rerun-script --save-dev

usage

Usage: rerun-script [options]

Options:

  -h, --help                   output usage information
  -V, --version                output the version number
  -d, --directory [directory]  package directory

configure package.json

  • NOTE 1: While the examples below use the standard lint checker, you are free to use any lint checker you like.
  • NOTE 2: The watch script in package.json is optional and is only necessary if you plan to invoke rerun-script via npm run. You can use any script name you like.

package.json

compact (recommended) format:
{
    "scripts": {
        "test": "node test.js",
        "lint": "standard",
        "watch": "rerun-script"
    },

    "watches": {
        "test": [ "*.js", "lib/**/*.js", "test/**/*.js" ],
        "lint": [ "*.js", "lib/**/*.js", "test/**/*.js" ]
    }
}
verbose format:
{
    "scripts": {
        "test": "node test.js",
        "lint": "standard",
        "watch": "rerun-script"
    },

    "watches": [
        {
            "script": "test",
            "patterns": [ "*.js", "lib/**/*.js", "test/**/*.js" ]
        },
        {
            "script": "lint",
            "patterns": [ "*.js", "lib/**/*.js", "test/**/*.js" ]
        }
    ]
}

If you only have one pattern to match for a script, you can pass in a string instead of an array:

{
    "scripts": {
        "test": "node test.js",
        "lint": "standard",
        "watch": "rerun-script"
    },

    "watches": {
        "test": "test/**/*.js",
        "lint": "*.js"
    }
}

start the watcher

# directly
$ ./node_modules/.bin/rerun-script

# or via `npm run watch`
$ npm run watch

screenshot

License

MIT