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

allrun

v1.0.4

Published

Execute multiple commands as parallel sub-processes. Optionally, first one finished terminates the rest.

Downloads

2

Readme

AllRun

CLI substitute for sh -c 'cmd1 & cmd2 & ...'
Works with linux, MacOS and Windows.

Execute multiple commands in parallel.
Use ctrl+c to terminate them.

Optionally

  • first one finished terminates the rest
  • log process ids, termination events and durations

No dependencies!

Installation

npm i -g allrun

Synopsis

Synopsis
   usage: allcmd [-k] [-v] <command>[ <argument>] [-- <command>[ <argument>]]
   usage: allnpm [-k] [-v] <script>[ <argument>] [-- <script>[ <argument>]]
   usage: allnode [-k] [-v] <file>[ <argument>] [-- <file>[ <argument>]]

Options:
   -k The first finished process terminates the rest
   -v Print process ids, termination events and runtime durations

Example:
   allcmd -kv sleep 1 -- sleep 3

Notice how -- is used to separate commands.

Example usage

Parallel CLI commands

Run two parallel cli commands in verbose mode

allcmd -v sleep 3 -- sleep 1 
Spawned [24480] sleep  [ '3' ]
Spawned [24481] sleep  [ '1' ]
Process [24481] terminated after 1012ms
Process [24480] terminated after 3004ms

Same as before, now the first finished process terminates the rest.

allcmd -kv sleep 1 -- sleep 10 
Spawned [24441] sleep  [ '10' ]
Spawned [24442] sleep  [ '1' ]
Process [24442] terminated after 1006ms
Process [24441] terminated after 1008ms

Parallel Node scripts

allnode script.js "with a single argument" -- ./another/script.js with multiple arguments

Parallel npm scripts

A local installation might be more suitable using npm i -D allrun.

Assuming you have two long running npm scripts you want to run in parallel.

allnpm build-watch -- test-watch

Example use in your package.json

"script": {
  "build-watch": "your watching build script",
  "test-watch": "your watching test script",
  "watch": "allnpm build-watch -- test-watch"
}