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

rigor

v1.0.0

Published

Simple portable static server

Downloads

2

Readme

rigor

A simple static server built with express and commander

Installation

Global

npm install -g rigor

Local

npm install --save rigor

Usage

Global

rigor ./my-directory

Local

Locally you need to use npm run to use the local version in the PATH. So you can just add a script to your npm package to run rigor. e.g.:

package.json

...
"scripts": {
  "serve": "rigor ./my-directory",
},
...

Process Managers

Chances are you may want to run the server as a process with something like pm2 or forever. To do this, you will need to set up a script to run rigor. e.g.:

start.sh

./node_modules/.bin/rigor ./my-directory

You'll notice that we've specified the relative path to rigor. This is only necessary if rigor is not global.

It also doesn't need to be a shell script, just make sure to set the relevant configuration on the process manager for whatever type of script you use.

Options

-s, --single

Flags the server as a single page application and will direct all asset requests to the index file.

-p, --port

Specify the port to use. Defaults to 8888

-i, --index

Specify the name of the index file. Defaults to index.html