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

browsenpm

v0.5.1

Published

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

Downloads

52

Readme

browsenpm.org

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

Installation

Browsenpm.org 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.

Running

npm start

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

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

Database

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 browsenpm.org accessible via balancers, make sure to only start npm-probe once. Set the environment variable PROBE=silent to prevent an instance from collecting data.

Cache

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

CACHE=flush:redis
CACHE=flush:couchdb

Debugging

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 |