Public | Automated Build

Last pushed: a year ago
Short Description
Full Description



A webservice that dishes out files from npm packages.

Inspired by npm-cdn,
unpkg,, and


$ git clone && cd ./cdn
$ npm install
$ node app


To access a file inside a published npm package, use the following pattern:{packageName}@{packageVersion}/{filePath}



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/foo@4.2.13,bar@3,baz.jswill return the4.2.13's version offoo, the latest version of the3rd major version ofbarand the latest version ofbaz`.

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/lodash@3.10.1(collection/pluck).js.
It is also possible to load several files from a package: /bundle/lodash@3.10.1(array/fill+collection/pluck).js.


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


MIT © Zoltan Kochan


Docker Pull Command
Source Repository