npm plugin: issues with legacyAuth

Describe the bug

Setting legacyAuth to true in auto config, does not properly send the value of _auth to npm publish.

To Reproduce

1. setup a npm project to use auto and the npm plugin
2. set legacyAuth to true in the plugin field
3. set publishConfig.registry in your package.json to be an external registry
4. make a .env file, add in NPM_TOKEN
5. run npx auto canary and see below error:

Error: Running command 'npm' with args [publish, --tag, canary, --_auth, MASKED_NPM_TOKEN] failed

npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The first argument must be one of type string, Buffer, ArrayBuffer, Array, or Array-like Object. Received type boolean

(MASKED_NPM_TOKEN being the actual value from .env’s NPM_TOKEN)

Expected behavior

Should be passing the token correctly to npm publish.

Additional context

Looking at this block of code, it passes to execPromise, and the token is considered an argument and not the value.

If I changed those lines to the below, all is functional:

return [
    options.isMonorepo ? "--legacy-auth" : "--_auth" + `=${process.env.NPM_TOKEN}`,
];

[sethomas]

ah you want me to fork, one moment

[adierkens]

🚀 Issue was released in v10.11.0 🚀