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

nodectl

v0.3.12

Published

supervisor script for node.js

Downloads

41

Readme

nodectl

supervisor sctipt for nodejs.

Features

  • watch code changes
  • cluster
  • daemonize
  • colorize console
  • env setter

Install

npm install -g nodectl

How to use

cd $HOME
express test
cd test
npm install
nodectl start app.js

watch

nodectl -w app.js

daemonise

nodectl -d app.js

both

nodectl -d -w app.js

stop daemon

cd ~/test
nodectl stop

daemonize and..

cd ~/test
nodectl start -d app.js
nodectl reload
nodectl restart
nodectl status
  application running.

Usage

nodectl [action] [options] <program>

Action

start

execute program (default action)

stop

stop daemonized program

restart

restart program with daemonize mode

force-clear

force clear pid

reload

release edited javascript (restart only child processes)

status

check program running or not

Options:

-p, --port [NUMBER]

default 3000, pass listening port (process.env.PORT)

-e, --env [STRING]

default development, pass environment (process.env.NODE_ENV)

-c, --cluster [NUMBER]

default number of cpu threads, concurrent process with cluster module

-P, --pidpath [STRING]

pid file location

-n, --nocolor

stop colorize console

-d, --daemon

daemonize process

-w, --watch

watch code changes, auto reload programs

-t, --test

check options (not execute)

-v, --version

show version and exit

-h, --help

show help message and exit

Defaults

  • [options] default from ${HOME}/.noserc.json
  • default from package.json: main

package.json search

nodectl automatically search nearest package.json form parent directories.

  • application name from package.json: name
  • application version from package.json: version
  • application main script from package.json: main