| 1 | Semver support for GitHub packages
|
| 2 | ----------------------------------
|
| 3 |
|
| 4 | This change adds support for public & private semver-friendly github tarballs.
|
| 5 |
|
| 6 | If you've ever tried using private github repositories instead of a private npm registry,
|
| 7 | you've probably failed. This fork of npm adds semver support for exactly that.
|
| 8 |
|
| 9 | For example the following [component](https://github.com/component/component)-style dependency definitions allow you to specify
|
| 10 | the username/repository, as well as the version - this is true for both public and
|
| 11 | private repos.
|
| 12 |
|
| 13 | ```json
|
| 14 | "dependencies": {
|
| 15 | "visionmedia/debug": "~0.7.0",
|
| 16 | "visionmedia/private": "1.x"
|
| 17 | }
|
| 18 | ```
|
| 19 |
|
| 20 | For authentiation you need to create an access token:
|
| 21 |
|
| 22 | 
|
| 23 |
|
| 24 | Then run:
|
| 25 |
|
| 26 | ```
|
| 27 | $ npm config set github-token <token>
|
| 28 | ```
|
| 29 |
|