f118062594
* Fix workflow * Trigger * [auto] Update compiled version * [auto] Commit modules * Push Windows changes * Fix * [auto] Update compiled version * Try removing cwd * [auto] Update compiled version * Try with path module * [auto] Update compiled version * Fix path * [auto] Update compiled version * Use raw path * [auto] Update compiled version * Other path * [auto] Update compiled version * Avoid @action/exec * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * Try with shelljs * [auto] Update compiled version * Fix my stupidity * Copy scripts to local dir * [auto] Update compiled version * Still use path * [auto] Update compiled version * Delete entrypoint.sh * [auto] Update compiled version * Make file executable * [auto] Update compiled version * Try using bash * [auto] Update compiled version
1.2 KiB
1.2 KiB
registry-url 
Get the set npm registry URL
It's usually https://registry.npmjs.org/, but configurable.
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
# .npmrc
registry = 'https://custom-registry.com/'
const registryUrl = require('registry-url');
console.log(registryUrl());
//=> 'https://custom-registry.com/'
It can also retrieve the registry URL associated with an npm scope.
# .npmrc
@myco:registry = 'https://custom-registry.com/'
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