Programmatic API for managing npm organization memberships and roles
74
Configure npm CLI defaults for registries and authentication tokens so installs use the right endpoints with persistent credentials.
@generates
/**
* Configures npm registry settings and authentication.
* @param {object} options - Registry and auth preferences.
* @param {string} options.registryUrl - Default registry URL to apply.
* @param {boolean} [options.alwaysAuth=false] - Whether installs should always send credentials.
* @param {string} [options.scope] - Optional package scope to map to a scoped registry.
* @param {string} [options.scopedRegistryUrl] - Registry URL to use for the provided scope.
* @param {string} [options.authToken] - Auth token to store for the relevant registry host.
* @param {string} [options.configPath] - Optional override path for the npm config file to write.
* @param {boolean} [options.verifyLogin=false] - Whether to check the authenticated username after writing config.
* @returns {Promise<{ configPath: string, username?: string }>} Details about where config was written and, if requested, who is authenticated.
*/
export async function configureNpm(options);Command-line client for the Node package registry; use it to write configuration and authenticate with registries. @satisfied-by
Install with Tessl CLI
npx tessl i tessl/npm-libnpmorgdocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10