Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Read matchers from config file #13

Closed
wants to merge 2 commits into from

Conversation

mjr9804
Copy link

@mjr9804 mjr9804 commented Sep 5, 2018

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:

{
  "matchers": ["npm ERR\\! cb\\(\\) never called\\!", "npm ERR\\! errno ECONNRESET",
               "npm ERR\\! shasum check failed", "npm ERR\\! code EINTEGRITY"]
}

Users can also create a ~/.npmretry.json or specify a path to a file with --configFile

@mjr9804 mjr9804 closed this Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants