Feature: Read matchers from config file #13
Closed
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.
Adds support for loading a custom config file that contains the matchers to be used in spotting certain NPM errors and triggering retries.
The goal is to make it simple for users to customize which NPM errors they need to match on without changing functionality of existing syntax.
By default, the same current list of supported matchers is loaded from
.npmretry.json
:Users can also create a
~/.npmretry.json
or specify a path to a file with--configFile