You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use the actions/setup-node step but in my specific case I have multiple scoped npm repositories with different registry urls,
According to your docs, it seems that there can only be a single registry url per setup-node step so I basically can't use it for my project.
Am I getting something wrong here or is it still not supported?
Thanks.
The text was updated successfully, but these errors were encountered:
You're on the right track here. Basically, there are 2 options available to you.
(1) Don't use setup-node for auth and just configure your .npmrc file separately. If you do this, I'd recommend not checking in your token and instead scoping in an env variable, so it would be something like //registry.npmjs.org:_authToken=${NODE_AUTH_TOKEN} then you would scope in a token. Note that you can still run setup-node to get the correct version of node installed, you'd just omit the registry input.
(2) If you don't need access to them in the same step, you can run setup-node in between different steps. e.g.
I'm trying to use the actions/setup-node step but in my specific case I have multiple scoped npm repositories with different registry urls,
According to your docs, it seems that there can only be a single registry url per setup-node step so I basically can't use it for my project.
Am I getting something wrong here or is it still not supported?
Thanks.
The text was updated successfully, but these errors were encountered: