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

wisk

v1.0.1

Published

Watch files or directories for changes, run tasks when these changes occur. Simple build tool that allows you to run shell commands when files or directories change.

Downloads

3

Readme

Wisk

Simple build tool that allows you to run shell commands when files or directories change.

Essentially chokidar + child_process.spawn.

Configuration

Create a file that defines the tasks. Wisk config files can be either js or json and must return an Array.

Here we set up a single watcher on the current directory that runs two tasks when any change is made.

// tasks.js
module.exports = [{
  paths: '.',  // The path to watch. Can be an array of paths and supports globs. See https://github.com/paulmillr/chokidar/blob/master/README.md#api
  options: {}, // `chokidar` watch options. See https://github.com/paulmillr/chokidar/blob/master/README.md#api
  on: {
    // Event listeners and the commands to run.
    // Listen for an FS event.
    // Available events: `add`, `addDir`, `change`, `unlink`, `unlinkDir`, `ready`, `raw`, `error`.
    // Additionally `all` is available which gets emitted with the underlying event
    // name and path for every event other than `ready`, `raw`, and `error`.
    all: ['date +%s', 'ls -al']
  }
}]

Example

module.exports = [{
  paths: ['client/**/*.js', 'client/**/*.html'],
  on: {
    all: ['npm run build:app:js']
  }
}, {
  paths: ['client/**/*.scss'],
  on: {
    all: ['npm run build:css']
  }
}]

CLI

Use wisk from the command line:

wisk tasks.js

This is the easiest way to use wisk. It loads the task.js file and starts watching for changes.

Command line options

  • cwd - the current working directory. Defaults to process.cwd()

API

Use wisk:

var wisk = require('wisk')
var tasks = require('./tasks')

wisk(tasks, __dirname)