npmcdn is a CDN for packages that are published via npm. Use it to quickly and easily load files using a simple URL like https://npmcdn.com/package@version/path/to/file.
A few examples:
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.
If you omit the file path, the main module will be served. This is especially useful for loading libaries that publish a UMD build as their main module.
Append a / at the end of a URL to view a listing of all the files in a package.
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.
Please note: 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.
| Name | Default Value | Description |
|---|---|---|
main |
main |
The name of the field in package.json to use as the main entry point when there is no file path in the URL (e.g. ?main=browser). |
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:
umd (or dist) directory to your .gitignore fileumd directory to your files array in package.jsonumd directory when you publishThat's it! Now when you npm publish you'll have a version available on npmcdn as well.
If you think this is useful, I'd love to hear from you. Please reach out to @mjackson with any questions/concerns.
Also, please feel free to examine the source on GitHub.