fix(#518): Find auth token associated to the registry #536
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
#518
β Type of change
π Description
This PR adresses a bug where the fetch request dosen't take the authToken of the found registry into account. This fix will use the .npmrc(s) to first find the registry and then search for an associated authToken.
Unfortunately npm.pkg.github.com dosen't support fetching a specific version like the NPM registry like:
/<pkgName>/latest
. So i we-wrote to use the/<pkgName>
endpoint and then find the desired version meta data.