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

pkgsrv

v1.0.2

Published

A server providing source packages based on semantic versioning

Readme

pkgsrv

Build Status codecov

A server providing source packages based on semantic versioning.

Installation

$ npm install pkgsrv

Command line options

|Option|Default|Description| |------|-------|-----------| |-b or --base|CWD + /packages|Set the base path of where packages are to be served up.| |-d or --debug|false|Enable a higher level of logging at a debug level and other diagnostic information.| |-l or --logs|false|Log events to a file.| |-p or --port|3000|The port that the server should listen on.| |-s or --subdomain| |Send logs to Loggly on the provided subdomain.| |-t or --token| |Authorisation token to utilise when sending log events to Loggly.|

How it works

The server is intended to stream modules of code to a client based on resolving a URL that can include a semver, a specific version, or a tag.

Semantic versions

For example, there is the following file structure:

packages
└─── pkgA
    ├─── 1.0.0
    │   │   index.ts
    ├─── 1.0.1
    │   │   index.ts
    ├─── 1.0.2
    │   │   index.ts
    ├─── 2.0.0
    │   │   index.ts
    └─── 2.0.1
        │   index.ts

And the request was made for http://localhost:3000/pkgA@^1.0.0/index.ts the client would be redirected to /[email protected]/index.ts and the packages/pkgA/1.0.2/index.ts would be streamed to the client.

Tags

Packages support a configuration JSON file which can express items like tags, which resolve to specific versions of the package. For example if there was a packages/pkgA/config.json that contained:

{
  "tags": {
    "latest": "2.0.0",
    "beta": "2.0.1"
  }
}

Then request was made for http://localhost:3000/pkgA@beta/index.ts the client would be redirected to /[email protected]/index.ts and the packages/pkgA/2.0.0/index.ts would be streamed to the client.

Specific versions

If the request was made for http://localhost:3000/[email protected]/index.ts the client would not be redirected and packages/pkgA/1.0.1/index.ts would be returned to the client.

Omitted semver or tag

If a request is made without any version or tag as part of the URL, if a config.json exists for the package, the latest tag version would be returned. If there is no config.json, the maximum version will be returned.

Namespace packages

The server supports named packages and namespaced packages. Namespaces will start with and @ symbol, which indicates the second part of the path is the package name.

For example http://localhost:3000/@ns/pkgA/index.ts would attempt to resolve the latest version of the package located in packages/@ns/pkgA.

License

pkgsrv is licensed under the MIT License and Copyright 2018 by Kitson P. Kelly.