feat: only return false on 404 in hasNpmPackage #96
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.
Currently, if the registry returns anything that is not a 200 status
code this function returns
false
. In the case where we are trying tocheck whether the package associated with a friendly name and the registry
returns a 503 this will result in fetching and installing
the wrong package.
i.e. Doing
heroku plugins:install api
@heroku-cli/plugin-api
existsapi
!!In this case, this is fairly harmless as that particularly library
doesn't do much. However, it could be used maliciously!
I think it may be better to re-raise the initial error in this scenario if we
can't be sure that the package does not exist.