Probably the easiest way to fix this would be to update the code that looks up the correct registry to pass to the -registry flag to check for 4 places Maybe we can use -registry only when is defined and delegate figuring out the correct registry to npm in all other cases. Mostly a note for me: I've done a quick test and it seems that npm info doesn't respect - which makes this very inconvenient for us because we can't simply rely on calling npm info either way. I will make sure to look it up in the implementation of npm. npmrc file encountered (not sure about this part). I think npmrc configs are also inherited from parent directories, so logic for loading those configs might need to traverse up the directory tree looking at each. npmrc is still picked up for scoped packages if there is no registry specific for this particular scope, right? And we always have a way to opt-out a package from a scoped registry by using publishConfig. npmrc file for the scope of the published packageĭoes this mean that if I opt-in into publishing a particular scope into a custom registry then it's sort of all-or-nothing? All packages of a given scope will pick this up? I guess this is similar to configuring registry and publishing a list of unscoped packages. When this gets picked up over registry?Ī scoped registry.
Would that be have no idea how to use this. However, this doesn't touch on what registry will be actually used - so if one wants to use a custom one then they should configure that separately. If I understand correctly - I can configure multiple auth tokens for multiple registries in a single file because keys for those always include the registry. Just to make sure that I understand this OK. I think I understand now better how those 2 play out together - but I have some follow-up questions. So I knew how to configure the authToken and in general how to configure the registry.
0 kommentar(er)
