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 🙏

© 2026 – Pkg Stats / Ryan Hefner

longrun

v7.0.1

Published

Run set of commands in group of directories

Readme

Longrun License NPM version Dependency Status Build Status Coverage Status

Run set of commands in group of directories. Based on runny.

Logo

Install

npm i longrun -g

How to use?

$ longrun
usage: longrun [command] [options]

Commands:
  init    Init runner
  add     Add current directory to runner
  run     Run commands from ~/.longrun.json
  remove  Remove current directory from runner
  list    List all runners
  clear   Clear directories list from runners
  finish  Remove runner(s)

Options:
  -v, --version  Show version  [boolean]
  -h, --help     Show help  [boolean]

Use example

First thing first, you should init new runner:

$ longrun init master -c "pwd"

Lets list what we have in master runner:

$ longrun list master
* master
> pwd
|  ~/longrun

Great. Now lets add another directory:

$ cd ../cloudcmd
$ longrun add master
$ longrun list master
* master
> pwd
|  ~/longrun
|  ~/cloudcmd

Now we can execute master runner with:

$ longrun run master
/home/coderaiser/longrun
/home/coderaiser/cloudcmd

Nice! Lets add one more runner to make things more fun:

$ longrun init who -c whoami
$ longrun list
master
who

And execute it:

$ longrun run -a
/home/coderaiser/longrun
/home/coderaiser/cloudcmd
coderaiser

As you see you can add as much runners as you wish, and run one or all of them.

How it works?

From the inside ~/.longrun.json it is just an array of runny objects that could be easily edited with text editor:

[{
    "command": "pwd",
    "directories": [
        "~/longrun",
        "~/cloudcmd"
    ]
}, {
    "command": "whoami",
    "directories": [
        "~/cloudcmd"
    ]
}]

Programmatical use

const longrun = require('longrun');

const runner = longrun([{
    command: 'pwd',
    directories: [
        '~/longrun',
        '~/cloudcmd',
    ],
}]);

runner.on('data', (data) => process.stdout.write(data))
    .on('error', (error) => process.stderr.write(error))
    .on('exit', () => console.log('exit'));

Special Thanks

License

MIT