-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
support negated glob for node_modules and always exclude node_modules #17
Comments
doesn't this revert #10 ? |
@JaKXz Read the linked discussion: istanbuljs/nyc#348 |
@sindresorhus I did, but the solution is unclear to me. Anyway, I'm not blocking this issue in any way, was just curious. |
@JaKXz How is it unclear? Put |
@JaKXz this will be a breaking change 👍 but, I'm convinced by my conversation with @sindresorhus (and by frequent |
@sindresorhus the "unclear"ness was because I was confused about if we're attempting to support both at the same time [which is slightly impossible 😆 ] - when we were implementing #10 I/we should have remembered how globs work and simply provided that documentation. Thanks for raising the issue. |
Addressed in |
@sindresorhus @JaKXz this will be released in istanbuljs/nyc#442 |
@bcoe Awesome. Thanks for fixing :) |
It's surprising behavior that when you set a custom
exclude
rule you almost always need to addnode_modules
. We should instead using a negated glob if folks want to instrumentnode_modules
.See the discussion with @sindresorhus in istanbuljs/nyc#348
The text was updated successfully, but these errors were encountered: