Sha256: d02eb5f48c1653a19520c6cd35ace0800cb93482c35a9f0a67670a6e0f4cf908
Contents?: true
Size: 1.17 KB
Versions: 62
Compression:
Stored size: 1.17 KB
Contents
# 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 var 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 var 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)
Version data entries
62 entries across 62 versions & 1 rubygems