Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

_auth in .npmrc needs to be scoped to a registry when using Node 18 #668

Closed
henninggross opened this issue Mar 1, 2023 · 0 comments · Fixed by #669
Closed

_auth in .npmrc needs to be scoped to a registry when using Node 18 #668

henninggross opened this issue Mar 1, 2023 · 0 comments · Fixed by #669
Labels
enhancement New feature or request

Comments

@henninggross
Copy link
Member

When using the node18-npm-toolset the following warning is logged:

Configuring npm to use Nexus (https://...) ...
npm WARN config `_auth`, `_authToken`, `username` and `_password` must be scoped to a registry. see `npm help npmrc` for more information.

Running npm help npmrc gives the following:

In order to scope these values, they must be prefixed by a URI fragment.
If the credential is meant for any request to a registry on a single host, the scope may look like //registry.npmjs.org/:.
If it must be scoped to a specific path on the host that path may also be provided, such as //my-custom-registry.org/unique/path:.

We should update the npm config to have a scoped _auth value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants