You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some patterns will not work, when there is a "not match" pattern before them.
OS:Windows 7.
// The 3rd pattern in this example doesn't work.
watch(['src/**', '!src/**/*.js', 'src/**/*.min.js'], function (vinyl) {
console.log('[watcher]', vinyl.relative);
});
// This still doesn't work
var watcher = watch(['src/**', '!src/**/*.js'], function (vinyl) {
console.log('[watcher 1]', vinyl.relative);
});
watcher.add('src/**/*.min.js');
// I use this way to around this bug.
watch(['src/**', '!src/**/*.js'], function (vinyl) {
console.log('[watcher 1]', vinyl.relative);
});
watch(['src/**/*.min.js'], function (vinyl) {
console.log('[watcher 2]', vinyl.relative);
});
The text was updated successfully, but these errors were encountered:
Let me make sure I understand correctly: you want negative globs to be processed in the order they appear in the patterns array, similarly to what I have implemented in gulp's glob-stream? (gulpjs/glob-stream#25 / gulpjs/glob-stream#27)
I believe it may be the case that gulp-watch's underlying file system watcher—Chokidar—always executes negative globs last, so that's why your sample fails. Please file a feature request in the Chokidar repository.
Some patterns will not work, when there is a "not match" pattern before them.
OS:Windows 7.
The text was updated successfully, but these errors were encountered: