unpkg/modules/client/components/Home.md

npmcdn is a fast, global content-delivery network for stuff that is published to npm. Use it to quickly and easily load files using a simple URL like:

`https://npmcdn.com/package@version/file`

A few examples:

• https://npmcdn.com/react@15.0.1/dist/react.min.js
• https://npmcdn.com/react-dom@15.0.1/dist/react-dom.min.js
• https://npmcdn.com/history@1.12.5/umd/History.min.js

You may also use a tag or version range instead of a fixed version number, or omit the version/tag entirely to use the latest tag.

• https://npmcdn.com/react@^0.14/dist/react.min.js
• https://npmcdn.com/react/dist/react.min.js

If you omit the file path, npmcdn will try to serve the browser bundle if present, the main module otherwise.

• https://npmcdn.com/jquery
• https://npmcdn.com/angular-formly
• https://npmcdn.com/three

Append a / at the end of a URL to view a listing of all the files in a package.

• https://npmcdn.com/lodash/
• https://npmcdn.com/modernizr/
• https://npmcdn.com/react/

You may use the special /bower.zip file path in packages that contain a bower.json file to dynamically generate a zip file that Bower can use to install the package.

• https://npmcdn.com/react-swap/bower.zip
• https://npmcdn.com/react-collapse@1.6.3/bower.zip

We do NOT recommend JavaScript libraries use Bower. Bower places additional burdens on JavaScript package authors for little to no gain. npmcdn is intended to make it easier to publish code, not harder, so Bower support will be removed in January 2017. Please move to npm for installing packages and stop using Bower before that time. See here for our rationale.

Query Parameters

Name	Default Value	Description
`main`	`browser`, `main`	The name of the field in [package.json](https://docs.npmjs.com/files/package.json) to use as the main entry point when there is no file path in the URL.
`json`	`undefined`	Return metadata about the resource at the current URL as JSON (e.g. `/any/path?json`). For directories, this generates a recursive listing of all files in the directory.

All other query parameters are invalid and will result in a 403 Forbidden response. This helps preserve the integrity of the cache for URLs with valid query strings.

Suggested Workflow

For npm package authors, npmcdn relieves the burden of publishing your code to a CDN in addition to the npm registry. All you need to do is include your UMD build in your npm package (not your repo, that's different!).

You can do this easily using the following setup:

• Add the umd (or dist) directory to your .gitignore file
• Add the umd directory to your files array in package.json
• Use a build script to generate your UMD build in the umd directory when you publish

That's it! Now when you npm publish you'll have a version available on npmcdn as well.