
Product
A New Design for GitHub PR Comments
We redesigned our GitHub PR comments to deliver clear, actionable security insights without adding noise to your workflow.
npm-cli-login
Advanced tools
Allows you to log in to NPM without STDIN, STDOUT. Use in places like CI build systems. Also creates/modifies entries in the ~/.npmrc file for authentication.
Allows you to log in to NPM without STDIN, STDOUT. Use in places like CI build systems. Also creates/modifies entries in the ~/.npmrc file for authentication.
npm install -g npm-cli-login
Use -g flag to use npm-cli-login via the CLI
npm-cli-login
expects the following environment variables to be set before you can use it to authenticate:
NPM_USER
: NPM usernameNPM_PASS
: NPM passwordNPM_EMAIL
: NPM emailNPM_REGISTRY
: (optional) Private NPM registry to log in to (Default: https://registry.npmjs.org)NPM_SCOPE
: (optional) Private NPM scopeNPM_RC_PATH
: (optional) Path to a custom .npmrc file you want to update (Default: ~/.npmrc
)Once the required ones are set, you can just run the following to log in:
npm-cli-login
You can also export variables and run it all in one line:
NPM_USER=testUser NPM_PASS=testPass NPM_EMAIL=test@example.com npm-cli-login
There is also support for command line arguments:
-u
: NPM Username-p
: NPM Password-e
: NPM Email-r
: NPM Registry-s
: NPM Scope--quotes
: Set to false
by default. Specifies whether your auth token requires quotes. This might required when your auth token has special characters, like =
, ?
etc.--config-path
: Set to ~/.npmrc
by default. Can be used to configure a custom .npmrc file to edit.For example: npm-cli-login -u testUser -p testPass -e test@example.com
Or: npm-cli-login -u testUser -p testPass -e test@example.com -r https://private.npm.com -s @privateNPM --quotes --config-path="./custom/path/"
Do note that at least one of the two ways must be configured, that is, you must either provide the required fields (username, password and email) using the environment variables or the command line arguments (or both)
To use the package programmatically, just require the module and pass in your NPM auth details as arguments:
var npmLogin = require('npm-cli-login');
npmLogin(username, password, email [, registry, scope, quotes, configPath]);
Logging in to the NPM registry:
var npmLogin = require('npm-cli-login'),
username = 'testUser',
password = 'testPass',
email = 'test@example.com'
npmLogin(username, password, email)
Logging in to private NPM registries:
var npmLogin = require('npm-cli-login'),
username = 'testUser',
password = 'testPass',
email = 'test@example.com',
registry = 'https://npm.example.com',
scope = '@myScope',
quotes = false,
configPath: './custom/path/'
npmLogin(username, password, email, registry, scope, configPath)
FAQs
Allows you to log in to NPM without STDIN, STDOUT. Use in places like CI build systems. Also creates/modifies entries in the ~/.npmrc file for authentication.
The npm package npm-cli-login receives a total of 55,847 weekly downloads. As such, npm-cli-login popularity was classified as popular.
We found that npm-cli-login demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
We redesigned our GitHub PR comments to deliver clear, actionable security insights without adding noise to your workflow.
Product
Our redesigned Repositories page adds alert severity, filtering, and tabs for faster triage and clearer insights across all your projects.
Security News
Slopsquatting is a new supply chain threat where AI-assisted code generators recommend hallucinated packages that attackers register and weaponize.