Support turning off node_modules default exclude via flag #172
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.
This PR is part of resolving issue #898. The idea is to be able to turn off the default exclusion of
**/node_modules/**
for users that need/want to support localnode_modules
. As mentioned in that issue, thenegateExclude
(i.e.!**/node_modules/**
) doesn't work for cases when you still want your exclusion list to still exclude matches within your localnode_modules
directory.Related PRs for solving the above issue:
NOTE: this test-exclude PR (istanbuljs/istanbuljs#213) will need to get merged and published before this is effective.