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 🙏

© 2024 – Pkg Stats / Ryan Hefner

flat-dependency-follower

v1.0.1

Published

follow npm registry updates, calculating flat dependency graphs

Downloads

2

Readme

An npm registry follower that calculates (and recalculates) flat package dependency manifests for each registry update. Users can query the manifest of any package at any version at any CouchDB-style update sequence number.

WARNING: Highly experimental dilettante technology! Any resemblance to real, usable npm package dependency graphs is purely coincidental.

Flat package manifests are shaped like:

[
  // "Dependency Records"
  {
    name: String,
    version: String, // SemVer version or URL
    // Optional.  Indicates the package is a direct dependency.
    range: String, // SemVer range or URL
    links: [
      // "Link Records"
      {
        name: String,
        version: String, // SemVer version or URL
        range: String // SemVer range or URL
      }
      // ...
    ]
  }
  // ...
]

The package ships with a bin script that starts following the public registry and serves data via HTTP.

Useful request paths include:

  • GET /package/$name/$version/$sequence, where /$sequence is the server's current sequence by default. Serves a flat dependency tree, if any, as JSON.

  • GET /sequence serves the server's current sequence number.