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

jointly

v0.0.2

Published

Run multiple processes in parallel.

Downloads

30

Readme

Run multiple processes from a single terminal.

npm install jointly --save-dev

Create a configuration jointly.config.json (or jointly.config.js) with tasks that should be executed:

[
  {
    "command": "ping",
    "args": ["google.com"]
  },
  {
    "command": "ping",
    "args": ["amazon.com"]
  }
]

To start tasks run:

jointly

You can explicitly pass a configuration file path:

jointly another.config.json

Configuration

Each task supports following options:

Determines when the task is considered fulfilled and allows its dependants to start:

  • 'start' then dependants start immediately after this command is started.
  • 'exit' then dependents start only after the command exits.
  • The callback that receives a line that command printed to the stdout and returns true if dependent tasks should be started, or false otherwise.

Determines when the task is considered failed:

  • 'auto' then the task is failed if the command exit code isn't 0.
  • 'never' then the task is never failed.
  • The callback that returns true is the task must be considered failed for a particular exit code.

The object with environment key-value pairs. By default, process.env is passed to a spawned task process.

Explicitly set the value of argv[0] sent to the child process. This will be set to command if not specified.

If false, then no shell is available. If true, runs command inside of a shell. Uses '/bin/sh' on Unix, and process.env.ComSpec on Windows. A different shell can be specified as a string. See Shell requirements and Default Windows shell.

No quoting or escaping of arguments is done on Windows. Ignored on Unix. This is set to true automatically when shell is specified and is CMD.