Ensure malformedRegistryResponse errors always have a dependency name #6455
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.
Summary
It's relatively common to see
Received malformed response from registry for undefined
errors, where theundefined
is coming from the fast that the returned body was totally invalid JSON, and therefore the package name couldn't be parsed from it.This PR ensures that a package name will always be show in such errors.
Test plan
A new test checks that the dependency name is included in the error message for malformed responses, even if it was not returned by the registry.