support --token=npmToken in lerna Publish

Expected Behavior

since npm publish cannot use NPM_TOKEN as environment, user must write token into .npmrc in order to do lerna publish in CI|CD environment, which is kind of annoying, I think pass token as parameter is more convenient just like what beachball is doing https://microsoft.github.io/beachball/ci-integration

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

lerna.json

<!-- Please paste your `lerna.json` here -->

lerna-debug.log

<!-- If you have a `lerna-debug.log` available, please paste it here -->
<!-- Otherwise, feel free to delete this <details> block -->

Context

Your Environment

Executable	Version
lerna --version	VERSION
npm --version	VERSION
yarn --version	VERSION
node --version	VERSION

OS	Version
NAME	VERSION

[kylemh]

If I put //registry.npmjs.org/:_authToken=${NPM_TOKEN} into a root-level .npmrc and try to commit without a valid NPM_TOKEN in my path, I get an error saying:

error An unexpected error occurred: "Failed to replace env in config: ${NPM_TOKEN}".

I understand why this happens, but this would be preventative for somebody working in this repo in an open source capacity - they wouldn’t be able to contribute.

edit: looks like I can do this in a GH action:

      - run: echo //registry.npmjs.org/:_authToken=${NPM_TOKEN} > .npmrc
        env:
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

[evocateur]

lerna publish supports the exact same pattern as npm publish with respect to environment variables in npmrc files. Once NPM_TOKEN is configured in the CI variables, add this to your project root .npmrc file:

//registry.npmjs.org/:_authToken=${NPM_TOKEN}

Note that the only .npmrc file respected by Lerna is the project root. Per-package (leaf node) npmrc files are ignored entirely. There’s also nothing special about the NPM_TOKEN variable name, it’s just a convention.