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 🙏

© 2025 – Pkg Stats / Ryan Hefner

tempwork

v0.7.2

Published

A webserver to spawn temporary workers

Downloads

17

Readme

ATTENTION: Tempwork has been renamed "Hat Rack"

New Github Repository

New NPM Package

tempwork

A simple server for launching mini-apps temporarily.

tempwork will map URL prefixes to launch simple web service commands you configure and proxy requests to them. They'll be terminated after 10 seconds, but restarted if more requests come in to them.

tempwork is a prototype, but has a short and robust time line:

  • Configurable timeout with keep-alive as requests come in
  • Static file configuration for services
  • Logging about worker lifespan
  • Recycling ports when the max port number is reached

tempwork is useful if you build lots of mini-projects, want to host them all somewhere, but none of them will get traffic often enough to support running 24/7.

Usage

npm install -g tempwork
tempwork --config=tempwork.conf

Where tempwork.conf is a YAML file like this:

workers:
  test_worker:
    command: "node"
    arguments:
      - "testworker.js"
    prefix: "test"
    port_env: "PORT"
  someproject:
    host: "www.someproject.local"
    cwd: "~/projects/someproject/"
    env:
      PATH: "~/.virtualenvs/someproject/bin/:~/projects/someproject/node_modules/.bin/"
    command: "~/.virtualenvs/someproject/bin/python manage.py runserver $PORT"
  default:
    static: "noservice.html"

workers defines one or more workers and must define a "default" worker.

command is a command to run to launch the worker if it is not working, and will be run with the list of defined arguments. If the command has space-separated arguments, it will be run with a shell and ignores the arguments option.

prefix is the URL prefix that will be routed to this worker. The worker will not see the prefix.

port_env is an environment variable to launch the worker with defining what port number it should listen to.

host defines a hostname to route traffic from to the worker.

env defines one or more environment variables for the command.

cwd defines a current working directory to change to when running the worker.

static defines a file the service should read instead of launching a worker.