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

multilaunch

v1.1.1

Published

A command line client for launching and tracking multiple processes

Downloads

15

Readme

Multilaunch

This is a utility for launching multiple processes and toggling between them to view their logs.

Screencast

Usage:

npx multilaunch config.json

Example config:

[
    {
        // name for the command in the sidebar
        "name": "Start Backend", 
        // the shell command to run
        "command": "rush start-backend", 
        // the cwd to run from
        "cwd": "./backend", 
         // if applicable, a string to look for to indicate the process has started up
        "startedWhen": "Server ready at",
        // a section for grouping commands under a section heading, commands still need to be consecutive
        // the section is rendered when it is different from the previous command's section
        "section": "Backend"
    },
    {
        "name": "Start Frontend",
        "command": "rush start-frontend",
        "cwd": "./frontend",
        "startedWhen": "Compiled successfully!",
        "section": "Frontend"
    }
]

When started, usage is fairly self-explanatory:

  • Up/Down to navigate
  • Enter to start/restart a process
  • Ctrl+C to stop a process
  • D to dump the current log to disk
  • Esc to quit multilaunch (and stop underlying processes)
  • [/] to scroll/up and down in the log (shift for faster scrolling)
  • Space to go back to the bottom of the log

Mouse scroll moves the log up and down, but you mean need to tweak terminal settings for this. Cmder - under Keys & Macro > Mouse > Send mouse events to console iTerm2 - Profiles > Terminal > Uncheck 'Save lines to scrollback in alternate screen mode'