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

foso-cdn

v0.1.1

Published

A webservice that dishes out files from npm packages.

Readme

foso-cdn

A webservice that dishes out files from npm packages.

Inspired by npm-cdn, wzrd.in, brcdn.org and jsdelivr.

Dependency Status Build Status Coverage Status npm version

Installation

$ git clone https://github.com/fosojs/cdn.git && cd ./cdn
$ npm install
$ node app

Usage

To access a file inside a published npm package, use the following pattern:

http://cdn.foso.me/raw/{packageName}@{packageVersion}/{filePath}

Examples:

Indexes

When a package is downloaded, index files are generated in HTML and JSON format.

Accessing packages

Any npm package can be loaded through the /bundle/{bundleRoute} endpoint. The bundleRoute should end either with .js or .css and should contain a list of one or more packageRoutes. For example, /bundle/foo,bar,baz.js will return a JavaScript file that is a concatenation of the latest versions of foo, bar, baz.

Loading specific versions

Sometimes it might be necessary to load a specific version of a package. In order to do so, it is possible to specify the version of the package after a @ character. For example, /bundle/[email protected],bar@3,baz.js will return the 4.2.13's version of foo, the latest version of the 3rd major version of bar and the latest version of baz.

Loading specific files

By default, the main file of the package is loaded (the path to the main file is stored in the "main" field for js and in the "style" field for css, in the package.json file). However, it is possible to load any file of a package by specifying the path to it. E.g., to load the collection/pluck.js file of the lodash package, this URL can be used: /bundle/[email protected](collection/pluck).js. It is also possible to load several files from a package: /bundle/[email protected](array/fill+collection/pluck).js.

Minifying

It is possible to minify the resources by adding .min to the end of their path. For instance:

License

The MIT License (MIT)