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-in-every

v0.2.0

Published

Run commands in every target projects/directories.

Downloads

42

Readme

NPM Package Build Status

Run in Every

A simple command line utility for running commands in specific projects or directories.

Installation

yarn add --dev run-in-every

Usage

run-in-every [target-name] [...options] -- command [...args]

For example:

run-in-every eslint-project --echo --parallel -- eslint --config {configFileName} .

Common Options

  • --bail (-b) exit immediately upon failure.
  • --quiet (-q) silence user command output.
  • --echo (-e) echo run-in-every output.
  • --parallel (-p) run commands in parallel.
    • --concurrency <number> concurrency for parallel mode.

Supported Targets

ESLint Project

Target name eslint-project, alias eslint.

options

  • --nested include nested-projects.

variables

  • configFileName file name of the matched config file (Path.basename()).

TSLint Project

Target name tslint-project, alias tslint.

options

  • --nested include nested-projects.

variables

  • configFileName file name of the matched config file (Path.basename()).

TypeScript Project

Target name ts-project, alias ts.

run-in-every ts-project -- tsc

options

  • --include-variant <pattern> include variant tsconfig.<pattern>.json.
  • --only-variant <pattern> only variant tsconfig.<pattern>.json.
  • --include-composite include composite projects (extends is not handled).
  • --only-composite match only composite projects (extends is not handled).

variables

  • configFileName file name of the matched config file (Path.basename()).

Directory

Target name directory.

options

  • --pattern <string> glob pattern of directory name.

variables

  • dirName directory name of the matched directory (Path.basename()).

Directory with File

Target name directory-with-file.

E.g.:

run-in-every directory-with-file --pattern '*/**/package.json' --data script.build -- pwd
run-in-every directory-with-file --pattern '*/**/config.json' --data 'host: "localhost"' -- pwd

options

  • --pattern <string> glob pattern of file to match.
  • --data <string> data pattern of file to match, format: <key>[:<value>][,...], e.g.: 'name: "run-in-every", version: "0.1.0"'.
    • <key>:
      1. Plain string will be split as path keys, e.g. scripts.build.
      2. JSON string array will be directly treated as path keys, e.g. ["scripts", "build"].
    • <value>: JSON value to be compared with _.isEqual.
    • If <value> is absent, it tests whether the path exists.

variables

  • fileName file name of the matched file (Path.basename()).

License

MIT License.