browsenpm / 0.5.1 last updated a year ago created on May 6th 2014


npm install --save browsenpm


git clone

dependencies show all 637

main async 0.9.2 MIT
bigpipe 0.8.5 MIT
bigpipe-layout 0.1.0 MIT
bigpipe-watch 0.1.1 MIT
connect 2.15.0 MIT

maintainers +2 more

npm-probe npm-probe
swaagie swaagie
jcrugzz jcrugzz
indexzero indexzero
v1 v1
3rdeden 3rdeden

versions 11 total

0.5.1 2 years ago V1
0.5.0 2 years ago V1
0.4.0 2 years ago V1
0.3.1 2 years ago swaagie
0.3.0 2 years ago V1
0.2.12 2 years ago swaagie
0.2.11 2 years ago swaagie
0.2.10 2 years ago swaagie
0.2.9 2 years ago swaagie
0.2.8 2 years ago swaagie
0.2.7 2 years ago npm-probe
22 Downloads yesterday.


Browse packages, users, code, stats and more the public npm registry in style.

Installation has several dependencies to run locally for development purposes.

sudo apt-get install redis-server couchdb
npm install

After update the configuration in development.json and provide the details needed. Note that your database might require authentication credentials.


npm start

# Or run the server by specifying a configuration file.
bin/server -c

Providing a custom configuration is optional. By default development.json will be used.


Both Redis and CouchDB should be running to cache data for certain pagelets. Make sure you run them locally or provide a server that runs either.

CouchDB will be used to cache all the data of npm-probe. The views in plugins/couchdb.json should be available on the database to ensure the pagelet can fetch the data. These views will be added to the browsenpm database on startup.

Status npm-mirrors

The current registry status is provided via npm-probe. Several probes are run at set intervals. The publish probe requires authentication with npm-probe. These credentials can (and are) provided to the configuration of the npm-probe instance.

npm-probe is provided with a CouchDB cache instance. All data is stored in the database browsenpm.

When running multiple instances of accessible via balancers, make sure to only start npm-probe once. Set the environment variable PROBE=silent to prevent an instance from collecting data.


During development it might be useful to destroy cached data, simply set any of the following environment variables to flush cache.



Most components have debug statements to help debugging, shortlist:

Module Description Statement
bigpipe all components DEBUG=bigpipe:*
bigpipe server DEBUG=bigpipe:server
bigpipe pages DEBUG=bigpipe:page
bigpipe pagelets DEBUG=bigpipe:pagelet
npm-probe statistics DEBUG=npm-probe
dynamis cache layer DEBUG=dynamis
ALL every module DEBUG=bigpipe:*,dynamis,npm-probe
Resolving all dependencies.. This could take a while as our cache is not yet fully warmed up.