Hi @paulmillr I think you have a problem on your latest release 3.0.1 and some others :
currently on your master's index.js the part of the code where the directoryFilter is evaluated is correct :
as in the method normalizeFilter, all negative should use negative.some instead of negative.every (I tested it locally).
but when installing several releases from NPM (so far I've tried 3.0.1, 3.0.0 and 2.0.1) the code installed contains negative.every, causing the directoryFilter to only work with a single entry (e.g. ['!.git']), while failing with many entries (e.g. ['!.git', '!node_modules']).
I can't open a PR as your code on master is correct, it looks like it's more a problem happening on releasing.
Roms1383
commented
5 years ago 
paulmillr
commented
5 years ago
Hi @paulmillr I think you have a problem on your latest release 3.0.1 and some others :
currently on your master's index.js the part of the code where the
directoryFilteris evaluated is correct :as in the method
normalizeFilter, allnegativeshould usenegative.someinstead ofnegative.every(I tested it locally).but when installing several releases from NPM (so far I've tried
3.0.1,3.0.0and2.0.1) the code installed containsnegative.every, causing thedirectoryFilterto only work with a single entry (e.g.['!.git']), while failing with many entries (e.g.['!.git', '!node_modules']).I can't open a PR as your code on master is correct, it looks like it's more a problem happening on releasing.
Hope this helps 😊