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

script-runner

v0.1.8

Published

Invoke multiple commands, running in parallel / sequential, matching npm scripts

Downloads

69

Readme

Script runner

Invoke multiple commands, running in parallel / sequential, matching npm scripts

Install

npm install --save-dev script-runner

Usage

usage: run [<options> [cmd..]..]


options:
-h, --help         output usage information
-v, --verbose      verbose logging (not implemented yet)
    --silent       suppress output of children
    --no-errors    also suppress error-output of children
-t, --test         no running only show process structure
-s, --sequential   following cmds will be run in sequence
-p, --parallel     following cmds will be run in parallel
-i, --ignore       the following cmd will be ignored for --first, --wait and errors
-f, --first        only in parallel block: close all sibling processes after first exits
-w, --wait         only in parallel block: will not close sibling processes on error
-m, --master       only in parallel block: close all sibling processes when the following cmd exits. exitCode will only depend on master

run also looks in node_modules/.bin for cmds
run-para is a shorthand for run --parallel
run-seq is a longhand for run
run-npm will match cmd with npm script and replace them, usage of globs is allowed
e.g. 
    run-npm -p build:* -s deploy

Examples

run "echo 1" "echo 2"
run-para "echo 1" "echo 2"
run-npm build:*
run mocha
run-npm -p serve --master "run-npm 'sleep 1' test:e2e"
// package.json
"scripts": {
    ...
    "build": "run-npm build:*",
    "build:step1": "do something",
    "build:step2": "do another thing"
    ...
}

License

Copyright (c) 2016 Paul Pflugradt Licensed under the MIT license.