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

npfs-common-ui

v0.6.36

Published

The NPFS Common UI Modules

Readme

National Pandemic Flu Service - Common UI modules

Summary

A library for common UI modules which need to be included in multiple UI projects.

Install

$ npm install --save git+http://10.210.164.148/pandemic-flu/common-ui.git#develop

NPM Registry

  • Current URL: 52.18.224.94
  • IP locked, make sure your outbound ip is on the list

Deploying NPM registry

  • Setup https://github.com/burkostya/npm-registry

      docker pull burkostya/npm-registry:2.6.6
    
      sudo mkdir -p /opt/data/npm-registry
    
      docker run --name='npm-registry' -d \
        -e 'COUCHDB_ADMIN_LOGIN=xxxxx' \
        -e 'COUCHDB_ADMIN_PASSWORD=xxxxx' \
        -e 'LOGIN=xxxxx' \
        -e 'PASSWORD=xxxxx' \
        -p 5984:5984 -p 80:80 \
        -v /opt/data/npm-registry:/var/lib/couchdb \
        burkostya/npm-registry:2.6.6

Replace the 'xxxxx' with the correct details

Setting NPM registry

Either set it in the .npmrc by adding registry = http://52.18.224.94/ ,ie:

    echo "registry=http://52.18.224.94/" | tee -a ~/.npmrc

Or set via command line:

    npm config set registry http://52.18.224.94/

To unset:

    npm config set registry https://registry.npmjs.org/

Publishing

In the folder with package.json run:

    npm publish

this may error in follows

    npm ERR! need auth auth required for publishing
    npm ERR! need auth You need to authorize this machine using `npm adduser`

in which case run:

    npm adduser

Note: Publishing with the same version number will complain, so you will have to update the package.json each time.

add another user to be author to (need to be the original author):

    npm owner add user package

ie

    npm owner add dominic.wood npfs-common-gulp

Find latest versions

When inside a module with .npmrc set to the npfs registry url 52.... run:

  npm search npfs

Should output something like

  NAME               DESCRIPTION                     AUTHOR       DATE       VERSION KEYWORDS
  npfs-common-gulp   NPFS Common gulp Task and Utils =admin-user… 2015-08-11 0.0.1
  npfs-common-server common server functions         =admin-user… 2015-08-11 0.0.1
  npfs-common-ui     The NPFS Common UI Modules      =admin-user… 2015-08-11 0.0.3
  npfs-rules         The NPFS Rules for /rules       =admin-user… 2015-08-11 2.5.0

Note on testing

After configuring the private npm registry. Delete .npm in your home directory and check everything still works (this holds a cache of npm libs and may create false positives that the setup is working)