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

echolot

v1.0.3

Published

Recursive PM2 json app config file merger

Downloads

9

Readme

echolot.js Build Status npm

Motivation

Imagine you have a nodejs folder situation on your server like this

/var/www
|__ app1
|____ processes.json
|__ app2
|____ processes.json
|__ ...

Each of these processes.json is an instance of a PM2 json application declaration that hold the PM2 decralations for the app of its folder.

In order to start and stop all of them at the same time it would be nice to have a merged.json of all these .json files.

After the build the folder structure will look like

/var/www
|__ app1
|____ processes.json
|__ app2
|____ processes.json
|__ ...
|__ merged.json

And you could start all the processes from the /var/www folder with a simple

pm2 start merged.json

Installation

npm install echolot -g

Usage

echolot /var/www

Where /var/www is the folder that contains all your PM2 apps/subfolders.

To-do

  • Handle errors like a grown-up