on
method.lodash.debounce
.EPERM
error is triggered.ignore
and cwd
. Thanks @remy!awaitWriteFinish
.
Thanks @dsagal!CHOKIDAR_PRINT_FSEVENTS_REQUIRE_ERROR
envdisableGlobbing
option.close()
being called before ready
usePolling
mode by setting CHOKIDAR_USEPOLLING
env variableaddDir
events when using cwd
and alwaysStat
optionsadd
events for files within a renamed directoryatomic: true
user-customizableawaitWriteFinish
featuresstats
with awaitWriteFinish
option..getWatched()
method, exposing all file system entries being watchedawaitWriteFinish
methodology to change
events (in addition to add
)addDir
and unlinkDir
events under globs (#337, #401).unwatch()
(#374, #403)awaitWriteFinish
option behaviorcwd
option behavior on WindowsawaitWriteFinish
and cwd
are now compatible.watch()
and .add()
awaitWriteFinish
option.unwatch()
method and relative pathsignored
ignored
files/globs while cwd
option is setalwaysStat
option and removed files.close()
method in fs.watch
mode with persistent: false
optionwatch
, add
, and unwatch
methodsunwatch
method to turn off watching of previously watched pathsignored
option allowing regex, function, glob, or array
courtesy of anymatchcwd
option to set base dir from which relative paths are deriveddepth
option for limiting recursionalwaysStat
option to ensure
fs.Stats
gets passed
with every add/change eventready
event emitted when initial fs tree scan is done and watcher is
ready for changesraw
event exposing data and events from the lower-level watch modulesfollowSymlinks
option to impact whether symlinks' targets or the symlink
files themselves are watchedatomic
option for normalizing artifacts from text editors that use
atomic write methodspersistent: false
mode when change events occurfs.watch
mode that caused watcher to leak into cwd
followSymlinks
option, which defaults to true
fs.watch
atomic
option to normalize events from editors using atomic writes
raw
event which exposes data from the underlying watch methodfs.watch
instantiation failsready
event, which is emitted after initial file scan completesundefined
FSWatcher
properties to indicate they're privateconsole.log
statement.fs.watch
and fs.watchFile
as wellfs.watch
upon invocationnpm rebuild
on non-Macsunlink
instead of unlinkDir
ignored
option in fsevents modepersistent: false
./
addDir
and unlinkDir
events.Watcher#close
now also removes all event listeners.options.ignored
is two-argument function, it will
also be called after stating the FS, with stats
argument.unlink
is no longer emitted on directories.usePolling
option (default: true
).
When false
, chokidar will use fs.watch
as backend.
fs.watch
is much faster, but not like super reliable.ignoreInitial
option.add
and change
events as second
arguments.change
events before unlink
.ignoreInitial
that allows to ignore initial add
events.ignorePermissionErrors
that allows to ignore ENOENT etc perm errors.interval
and binaryInterval
that allow to change default
fs polling intervals.all
event that receives two args (event name and path) that combines
add
, change
and unlink
events.fs.watchFile
on node.js 0.8 on windows.unlink
event are no longer emitted for directories, for consistency with
add
.watch()
.chokidar.watch()
.