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

run-when

v1.1.0

Published

Run tasks based on git diff files

Downloads

320

Readme

run-when Build Status

Run tasks based on git diff files

Usage

Having this directory tree with the following files changed:

├── app
├────── components
├      ├── index.js
├      ├── app.jsx
└── __tests__
├      ├── app.spec.jsx
└── package.json

run-when will check glob rules against it and run tasks if any changes have been made.

Javascript

import runWhen from 'run-when';

runWhen([
  {
    glob: ['app/components/index.js', 'app/__tests__/**'],
    task(paths) {
      console.log('This will be called!');
    }
  },
  {
    glob: ['!package.json'],
    task(paths) {
      return Promise.resolve('You can return a promise from your task');
    }
  },
  {
    // Optionally pass changed files
    changedFiles: () => Promise.resolve(['app/index.js', 'app/components/header.jsx']),
    glob: ['app/components/**'],
    task(paths) {
      console.log(paths === ['app/components/header.jsx']);
    }
  }
]);

CLI

$ run-when '["app/components/**", "app/utils/**"]' 'echo running tests... && yarn test'
  • First argument is a stringified JSON containing glob patterns.
  • Second argument is the task to run.

How it works

By default run-when will use git to know which files have been changed. You can change that passing an array of files to changedFiles.

Globbing pattern

The library uses multimatch for the globbing matching (sindresorhus 😻). Just a quick overview:

  • * matches any number of characters, but not /
  • ? matches a single character, but not /
  • ** matches any number of characters, including /, as long as it's the only thing in a path part
  • {} allows for a comma-separated list of "or" expressions
  • ! at the beginning of a pattern will negate the match

Various patterns and expected matches.

Api

type Files = Array<string>;
interface Rule {
  glob: Array<string>,
  task: (results: Files) => void,
  changedFiles?: () => Promise<Files>
}
type runWhen = (rules: Array<Rule>) => Promise;

Installation

$ yarn add run-when -D