| Dir : /opt/alt/alt-nodejs14/root/lib/node_modules/npm/node_modules.bundled/registry-url/ |
| Server: Linux ngx353.inmotionhosting.com 4.18.0-553.22.1.lve.1.el8.x86_64 #1 SMP Tue Oct 8 15:52:54 UTC 2024 x86_64 IP: 209.182.202.254 |
| Dir : //opt/alt/alt-nodejs14/root/lib/node_modules/npm/node_modules.bundled/registry-url/readme.md |
# 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)