How to set npm credentials using `npm login` without reading from stdin?

Question

I'm trying to automate npm publish inside a Docker container, but I receive an error when the npm login command tries to read the username and email:

npm login << EOF username password email EOF 

It works in a Bash terminal, but in a container (without stdin) it shows error:

Username: Password: npm ERR! cb() never called! npm ERR! not ok code 0 

According to npm-adduser:

The username, password, and email are read in from prompts.

How can I run npm login without using stdin?

Answer 1

TL;DR: Make an HTTP request directly to the registry:

TOKEN=$(curl -s \   -H "Accept: application/json" \   -H "Content-Type:application/json" \   -X PUT --data '{"name": "username_here", "password": "password_here"}' \   http://your_registry/-/user/org.couchdb.user:username_here 2>&1 | grep -Po \   '(?<="token": ")[^"]*')  npm set registry "http://your_registry" npm set //your_registry/:_authToken $TOKEN 

Rationale

Behind the scenes npm adduser makes an HTTP request to the registry. Instead of forcing adduser to behave the way you want, you could make the request directly to the registry without going through the cli and then set the auth token with npm set.

The source code suggests that you could make a PUT request to http://your_registry/-/user/org.couchdb.user:your-username with the following payload

{   name: username,   password: password } 

and that would create a new user in the registry.

Many thanks to @shawnzhu for having found a more cleaner approach to solve the problem.

Answer 2

npm set //<registry>/:_authToken $TOKEN 

Example for Github Package Registry:

npm set //npm.pkg.github.com/:_authToken $GITHUB_TOKEN 

This is the simplest solution that I have found.