FM / registry-url

/usr/local/lib/node_modules/nodemon/node_modules/registry-url/

/usr/local/lib/node_modules/nodemon/node_modules/registry-url

Name	Size	Mode	Actions
index.d.ts	949	0644	edit dl rm
index.js	398	0644	edit dl rm
license	1109	0644	edit dl rm
package.json	1819	0644	edit dl rm
readme.md	1191	0644	edit dl rm

Edit: /usr/local/lib/node_modules/nodemon/node_modules/registry-url/readme.md (1191B)

# 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

cmd: