Catalog npm
PACKAGE EXPLORERView in registry

@0xproject/npm-cli-login

npm

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.

Versions collected1
Direct dependencies5From release 0.0.11
Last observed21 Oct, 09:33 UTC

README

Current package documentation

npm-cli-login Build Status

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.

Installation

npm install -g npm-cli-login

Use -g flag to use npm-cli-login via the CLI

Usage

CLI

npm-cli-login expects the following environment variables to be set before you can use it to authenticate:

  • NPM_USER: NPM username
  • NPM_PASS: NPM password
  • NPM_EMAIL: NPM email
  • NPM_REGISTRY: (optional) Private NPM registry to log in to (Default: https://registry.npmjs.org)
  • NPM_SCOPE: (optional) Private NPM scope
  • NPM_RC_PATH: (optional) Path to a custom .npmrc file you want to update (Default: ~/) (Do note this is the path of the file, not the file itself)

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 ~/ by default. Can be used to configure a custom .npmrc file to edit (Do note this is the path of the file, not the file itself)

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)

Programmatic API

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]);
Example

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)

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 1

Collected releases
VersionPublishedDirect dependenciesOpen version
0.0.11Registry latest17 Oct 20185

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
postmanlabs/npm-cli-login

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 21 Oct, 09:33 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:e896b104ebccf0ed497d3e6504f75786a320afdba7bafc0b94c206c6dbf56ace