blob: dfcb99ae58f54b4fa91eb6efd28960903fa21057 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
# registry-url [![Build Status](https://travis-ci.org/sindresorhus/registry-url.svg?branch=master)](https://travis-ci.org/sindresorhus/registry-url)
> Get the set npm registry URL
It's usually `https://registry.npmjs.org/`, but it's [configurable](https://docs.npmjs.com/misc/registry).
Use this if you do anything with the npm registry as users will expect it to use their configured registry.
## Install
```
$ npm install registry-url
```
## Usage
```ini
# .npmrc
registry = 'https://custom-registry.com/'
```
```js
const registryUrl = require('registry-url');
console.log(registryUrl());
//=> 'https://custom-registry.com/'
```
It can also retrieve the registry URL associated with an [npm scope](https://docs.npmjs.com/misc/scope).
```ini
# .npmrc
@myco:registry = 'https://custom-registry.com/'
```
```js
const registryUrl = require('registry-url');
console.log(registryUrl('@myco'));
//=> 'https://custom-registry.com/'
```
If the provided scope is not in the user's `.npmrc` file, then `registry-url` will check for the existence of `registry`, or if that's not set, fallback to the default npm registry.
## License
MIT © [Sindre Sorhus](https://sindresorhus.com)
|