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 🙏

© 2026 – Pkg Stats / Ryan Hefner

packer-server

v1.0.6

Published

Asset manager for native wrapped application

Readme

packer-server

  • Static File Server for the app files
  • clones the desired repository in the desired branch
  • listens for pushes to the branch (see git-spy and github-webhook-forwarding)
  • pulls the latests changes from the branch every time there is a push
  • more (TODO: document it)

Installation

$ npm i -g packer-server

Usage:

See configure and launch your service in vigour-config for information on how to configure and launch the packer-server and where to get more info for all the configuration options.

npm start

As a minimum, you must set the following configuration options:

  • repo (MAIL_MAN_REPO)
  • branch (MAIL_MAN_BRANCH)
  • gwfURL (GIT_SPY_GWF_URL)
  • gwfUser (GIT_SPY_GWF_USER)
  • gwfPass (GIT_SPY_GWF_PASS)

If serving an app found in a private repository, make sure you have the permissions to access it via the git command (this is what packer-server uses internally).

You will probably also want to set the following unless you're just launching a single packer locally for testing.

  • port (PACKER_SERVER_PORT)
  • gitSpyPort (GIT_SPY_PORT)

Other options are available (see the package)

npm test

Some of the tests will launch a real packer, which will try to subscribe to a github-webhook-forwarding service and need its URL and proper credentials. credentials we don't want to put in the repo. Please set the following environment variables instead:

  • GWF_TEST_OWNER
  • GWF_TEST_USER
  • GWF_TEST_PASS
  • GWF_TEST_PORT (optional, default: 8000)

example:

$ export GWF_TEST_OWNER=vigour
$ export GWF_TEST_USER=vigourbot
$ export GWF_TEST_PASS=OMGthisissoooooosecret

how it works:

  • mail-man clones the specified branch of the specified repo in the directory where you launched packer-server.
  • git-spy subscribes to the repo and branch on the github-webhook-forwarding process reachable via gwfURL, which registers a WebHook on GitHub to listen for pushes.
  • packer-server serves the files found at dist/<platform> of the cloned repo, where <platform> is selected by looking at the request's User-Agent header.
  • When a push is made to the specified repo and branch, the packer will pull and serve the new version automatically.