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

pincer

v5.1.1

Published

Pincer is a recursive static file server that serves content-types correctly and logs nicely.

Downloads

8

Readme

PinCer

P.inC.er stands for "Puny Server". Yes, I know.

PinCer is a recursive static file server that serves content-types correctly and logs nicely that runs on Node.js.

Its primary purpose is iteratively developing and debugging entirely static websites.

(Don't use PinCer in production environments.).

Usage Examples

Serve the current directory @ localhost:8000:

$ pincer

Serve the directory WEBROOT @ localhost:8000:

$ pincer [WEBROOT]

Serve the directory /var/www @ 0.0.0.0:8080:

$ CWDP=/var/www HOSTP=0.0.0.0 PORTP=8080 pincer

CWDP defaults to the current directory.

HOSTP defaults to localhost.

PORTP defaults to 8000.

N.B.: The WEBROOT argument takes precedence over the CWDP environment variable, if both are specified.

Show pincer's help message:

$ pincer [ --help | -h | --h ]

Show the current version of pincer:

$ pincer [ --version | -v | --v ]

Install

$ sudo npm install -g pincer

Why does this exist?

Because I was tired of writing the same static file server over and over again. Serving static files with express.js is nice, but it's like killing a bug with a forest fire.

pincer ins one-file small (~100 lines, excluding dependencies) and has super sane defaults.

Features

  • Recursive static file serving.
  • Serves Content-Types based on file extension (defaulting to text/plain if non-existent, or unknown)
  • Logs requested server route, and the correspondingly served file.
    • Logs file serving errors as well (non-existent file, etc.).
  • Serves files with the utf-8 charset.
  • One-file (~100 lines, excluding dependencies) small, so super extensible.