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

dictator

v0.3.4

Published

Process management for development

Downloads

34

Readme

dictator

Process management for development.

  • Start up processes in order
  • Configurable wait time to allow dependencies to start up properly
  • Colorized output (stdout & stderr)
  • If child exits, terminate everything
  • If dictator exits, terminate everything
  • Looks for dictator.json in current dir (or specify filename in first arg)

install

npm install -g dictator

usage

Create a dictator.json in the root of your project

{
  "redis": {
    "cmd": "redis-server",
    "args": ["--port", 1337],
    "color": "red",
  },
  "elasticsearch": {
    "cmd": "elasticsearch",
    "args": ["-f"],
    "color": "green",
    "wait": 3000
  },
  "some-node-server": {
    "cmd": "some-node-server",
    "deps": ["elasticsearch", "redis"],
    "color": "blue"
  },
  "some-rails-app": {
    "cwd": "rails-root",
    "cmd": "rails",
    "args": ["s"],
    "color": "yellow"
  },
  "env-var-app": {
    "cmd": "my-app",
    "env": {
      "SOME_VAR": "some-value"
    }
  }
}

Then run the dictator:

dictator [/path/to/dictator.json]

Will do the following:

  1. Start some-rails-app by changing the cwd to rails-root and runinng rails s and logging its output in yellow
  2. Start elasticsearch, log its output in green, wait 3000 to let it initialize
  3. Start redis-server, log its output in red
  4. Start some-node-server, log its output in blue

If any of the processes quit the others will receive a SIGKILL and dictator will exit.

exclude some services

dictator -e nope

run only some services

dictator -o yes -o indeed

pro tips

  • Set up a config directory next to your dictator.json and put all configuration in there
  • Set up a state directroy next to your dictator.json and configure your services to put all their state (DBs, logs, etc) in there
  • For a nice reset of the environment, simply: rm -rf state/* before running the dictator. Remove the current state and run the dictator. You get it? A coup. Ok, I'm stopping it.