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

npmserve-server

v0.0.2

Published

[![npm](https://img.shields.io/npm/v/npmserve-server.svg?maxAge=2592000)]()

Readme

npmserve-server

npm

This server provides npm as a service accessible via http endpoints. This allows virtual machines and other slow clients to offload the work of building node_modules and thus perform significantly faster installs.

disclaimer

npmserve and npmserve-server are experimental projects. These tools should not be used for deploying production dependencies. The client/server model does not yet have authentication or authorization in place. This project also does not guarantee the integrity or security of dependencies installed from npm or distributed to clients. Please consider your own requirements and constraints before incorporating npmserve into your workflow.

clients

  1. command-line client: available at npmserve.

  2. web interface: the server provides a web interface to delete and trigger builds:

web interface

implementation

To solve these problems, we are providing a server on which clients can execute their npm installs by uploading a package.json file. In response, they will receive a node_modules.tar.gz archive containing their install results.

limitations

Currently, the server must be run on a machine with the same architecture as the clients. If this is not the case, calls to /npm/install may return node_modules archives containing extensions compiled for the wrong architecture.

build semantics

To the extent possible, the npmserve server provides operations analogous to those that a user running npm locally might do. Users running locally often resort to forceful actions such as deleting their entire node_modules directory or clearing their cache. We provide the facility to perform those actions via the API as well. These are documented below.

API

POST /npm/install

  • behavior: performs an npm install on the server
  • arguments: packageJson: string of package.json file contents
  • content-type: application/x-www-form-urlencoded; charset=utf-8
  • response: compressed archive node_modules.tar.gz, containing node_modules

DELETE /npm/install/:hash

  • behavior: deletes the node_modules build on the server for the specified build hash
  • arguments: none
  • response: void

POST /npm/cache/clean

  • behavior: clears the .npm cache on the server
  • arguments: none
  • response: void

environment

This project relies on the following environment variables:

| name | type | default | description | | ---- | ---- | ------- | ----------- | | BUILD_DATA_DIR | string | ./data | path to the directory in which to store build data | | NPM_CONFIG_REGISTRY | string | https://registry.npmjs.org | the npm registry to use for npm install |