Gecko [ www.corporacionhdm.com.pe ]

Linux premium71.web-hosting.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64
LiteSpeed
Server IP : 198.187.29.8 & Your IP : 18.227.111.102
Domains : Cant Read [ /etc/named.conf ]
User : cleahvkv

Name	Size	Permission	Date
index.js	228 B	-rw-r--r--	2021-03-10 14:36
license	1.09 KB	-rw-r--r--	2021-03-10 14:36
package.json	1.64 KB	-rw-r--r--	2021-03-10 14:36
readme.md	1.18 KB	-rw-r--r--	2021-03-10 14:36

Rename

# 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 [configurable](https://www.npmjs.org/doc/misc/npm-config.html#registry).

Use this if you do anything with the npm registry as users will expect it to use their configured registry.

## Install

```
$ npm install --save 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