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

eternal

v0.0.1a

Published

Monitor and restart long-running node processes.

Downloads

3

Readme

#eternal

run things to eternity. It shouldn't matter what those runnable things happen to be.

##Options

--help, -h - show help
--version, -v - show version
--debug, -d - show verbose debugging output

##Commands:

####start [script]

Start a script. Usage: eternal start thing.js

If a service is already running with the same key (or filename without a key specified), the running service will be stopped and the new one started.

#####Options

--exec, -e - specify an executable.
Can be either absolute/relative path or a command found in $PATH
Defaults to node

--max, -m - specify max number of restarts. Set to 0 for infinite restarts
Defaults to 10

--log - Explicit path to logfile for this service's stdout/stderr. Defaults to ~/.eternal/.log

--key - identifier to use for the service. This identifier will be used in logs and commands. (recommended)

#####Examples:

Start a node app that will restart forever:
eternal start app.js -n 0

Start a ruby script:
eternal start script.rb -e ruby

Start a script with an identifier:
eternal start script.js --key stage_app

####stop [file]

Stop a script. Usage: eternal stop thing.js

If a key was specified in eternal start command, it should be used instead of filename.

#####Examples:

eternal stop app.js

eternal stop stage_app

####stopall

Stop all eternal services [for current user]. Usage: eternal stopall

####restart [file]

Restart a script. Usage: eternal restart thing.js

If a key was specified in eternal start command, it should be used instead of filename.

#####Examples:

eternal restart app.js

eternal restart stage_app

####restartall

Restart all currently monitored services. Usage: eternal restartall

####list

List all currently monitored services. Usage: eternal list

#####Options

--json - output JSON instead of pretty-printing

#TODO v0.1.0:

output modes -- pretty print, JSON

basic tests

Options:

  • --color, --nocolor - for better pretty-printing
  • --watch: watch files for changes and restart, with options as to which files are watched