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 🙏

© 2025 – Pkg Stats / Ryan Hefner

jointly

v0.0.3

Published

Run multiple processes in parallel.

Downloads

88

Readme

Run multiple processes from a single terminal.

Create a configuration file jointly.config.json, jointly.config.js, jointly.config.mjs (requires NodeJS 23+) or jointly.config.ts (requires NodeJS 23+) with tasks that should be executed:

{
  "$schema": "https://raw.githubusercontent.com/smikhalevski/jointly/refs/tags/v0.0.3/schema.json",
  "tasks": [
    {
      "command": "vite"
    },
    {
      "command": "tsc",
      "args": ["--watch", "--preserveWatchOutput", "--pretty"]
    }
  ]
}

To start tasks run:

npx jointly

You can explicitly specify a configuration file path:

npx jointly my_config.json

Environment variables

Specify environment variables for each task:

{
  "tasks": [
    {
      "command": "printenv",
      "args": ["HELLO"],
      "env": {
        "HELLO": "Hello world!"
      }
    }
  ]
}

Task dependencies

Tasks can depend on each other. Here's an example where tsc type checker is started in parallel with vite build, while docker waits for vite to emit built assets and then builds and starts the container.

export default {
  tasks: [
    {
      command: 'tsc',
      args: ['--watch', '--preserveWatchOutput', '--pretty'],
      resolveAfter: 'exit'
    },
    {
      key: 'vite-build',
      command: 'vite',
      args: ['build', '--watch'],
      
      // Receives each line vite outputs to stdout
      resolveAfter: line => line.includes('built in'),
    },
    {
      command: 'docker',
      args: ['compose', 'up', '--build', '--watch'],
      dependencies: ['vite-build'],
    }
  ]
}

All processes would proceed running in parallel until user prompt is closed.

Kill signal

Different processes may require different kill signals. Specify a kill signal for a task:

{
  "tasks": [
    {
      "command": "ping",
      "args": ["google.com"],
      "killSignal": "SIGTERM"
    }
  ]
}

By default, SIGINT is used, which is intended to interrupt the currently running process and return control to the user prompt.