Private registry as an environment variable or plugin config about npm

[pvdlg]

See conversation from #161

The registry can be set in an .npmrc file that can live in the home directory of the CI user. This way the registry config is associated with your environment rather than with the project.

Would that works for you?

[gr2m]

I’d like to be able to configure the registry for a different reason: I want to be able to publish the same package to both the npm registry as well as GitHub’s npm registry.

I’ve tried to use the NPM_CONFIG_REGISTRY environment variable but it isn’t used by this plugin.

Adding a configuration option would be the cleanest option I think. I’ll get a pull request going for further discussion

[semantic-release-bot]

🎉 This issue has been resolved in version 5.2.0 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀