- Allow semver range updates for upath dependency
- Fix #668 glob issue on Windows when using
ignore
andcwd
. Thanks @remy! - Fix #546 possible uncaught exception when using
awaitWriteFinish
. Thanks @dsagal!
- Breaking: Upgrade globbing dependencies which require globs to be more strict and always use POSIX-style slashes because Windows-style slashes are used as escape sequences
- Update tests to work with upgraded globbing dependencies
- Add ability to log FSEvents require error by setting
CHOKIDAR_PRINT_FSEVENTS_REQUIRE_ERROR
env - Fix for handling braces in globs
- Add node 8 & 9 to CI configs
- Allow node 0.10 failures on Windows
- Add
disableGlobbing
option - Add ability to force interval value by setting CHOKIDAR_INTERVAL env variable
- Fix issue with
.close()
being called beforeready
- Added ability for force
usePolling
mode by settingCHOKIDAR_USEPOLLING
env variable
- Fix missing
addDir
events when usingcwd
andalwaysStat
options - Fix missing
add
events for files within a renamed directory
- To help prevent exhaustion of FSEvents system limitations, consolidate watch instances to the common parent upon detection of separate watch instances on many siblings
- Make debounce delay setting used with
atomic: true
user-customizable - Fixes and improvements to
awaitWriteFinish
features
- Update async-each dependency to ^1.0.0
- Now correctly emitting
stats
withawaitWriteFinish
option.
- The watcher could now be correctly subclassed with ES6 class syntax.
- Add
.getWatched()
method, exposing all file system entries being watched - Apply
awaitWriteFinish
methodology tochange
events (in addition toadd
) - Fix handling of symlinks within glob paths (#293)
- Fix
addDir
andunlinkDir
events under globs (#337, #401) - Fix issues with
.unwatch()
(#374, #403)
- Improve
awaitWriteFinish
option behavior - Fix some
cwd
option behavior on Windows awaitWriteFinish
andcwd
are now compatible- Fix some race conditions.
- #379: Recreating deleted directory doesn't trigger event
- When adding a previously-deleted file, emit 'add', not 'change'
- Allow nested arrays of paths to be provided to
.watch()
and.add()
- Add
awaitWriteFinish
option
- Dependency updates including fsevents@1.0.0, improving installation
- Fix issue with
.unwatch()
method and relative paths
- Fix regression with regexes/fns using in
ignored
- Fix bug with
ignored
files/globs whilecwd
option is set
- Fix race issue with
alwaysStat
option and removed files
- Fix bug with absolute paths and ENAMETOOLONG error
- Fix bug with
.close()
method infs.watch
mode withpersistent: false
option
- Glob support! Use globs in
watch
,add
, andunwatch
methods - Comprehensive symlink support
- New
unwatch
method to turn off watching of previously watched paths - More flexible
ignored
option allowing regex, function, glob, or array courtesy of anymatch - New
cwd
option to set base dir from which relative paths are derived - New
depth
option for limiting recursion - New
alwaysStat
option to ensurefs.Stats
gets passed with every add/change event - New
ready
event emitted when initial fs tree scan is done and watcher is ready for changes - New
raw
event exposing data and events from the lower-level watch modules - New
followSymlinks
option to impact whether symlinks' targets or the symlink files themselves are watched - New
atomic
option for normalizing artifacts from text editors that use atomic write methods - Ensured watcher's stability with lots of bugfixes.
- Fix bug which breaks
persistent: false
mode when change events occur
- Fix bug with matching parent path detection for fsevents instance sharing
- Fix bug with ignored watch path in nodefs modes
- Fix bug in
fs.watch
mode that caused watcher to leak intocwd
- Fix bug preventing ready event when there are symlinks to ignored paths
- Fix handling of special files such as named pipes and sockets
- Fix recursive symlink handling and some other path resolution problems
- Fix a case where file symlinks were not followed properly
- Symlink support
- Add
followSymlinks
option, which defaults totrue
- Add
- Change default watch mode on Linux to non-polling
fs.watch
- Add
atomic
option to normalize events from editors using atomic writes- Particularly Vim and Sublime
- Add
raw
event which exposes data from the underlying watch method
- Fix a bug where an error is thrown when
fs.watch
instantiation fails
- Add a
ready
event, which is emitted after initial file scan completes - Fix issue with options keys passed in defined as
undefined
- Rename some internal
FSWatcher
properties to indicate they're private
- Fix some leftover issues from adding watcher reuse
- Remove accidentally committed/published
console.log
statement. - Sry 'bout that 😿
- Apply watcher reuse methodology to
fs.watch
andfs.watchFile
as well
- More efficient creation/reuse of FSEvents instances to avoid system limits
- Reduce simultaneous FSEvents instances allowed in a process
- Handle errors thrown by
fs.watch
upon invocation
- Limit number of simultaneous FSEvents instances (fall back to other methods)
- Prevent some cases of EMFILE errors during initialization
- Fix ignored files emitting events in some fsevents-mode circumstances
- Bump fsevents dependency to ~0.3.1
- Should resolve build warnings and
npm rebuild
on non-Macs
- Should resolve build warnings and
- Fix removed dir emitting as
unlink
instead ofunlinkDir
- Fix issues with file changing to dir or vice versa (gh-165)
- Fix handling of
ignored
option in fsevents mode
- Improve individual file watching
- Fix fsevents keeping process alive when
persistent: false
- Improve handling of text editor atomic writes
- Many stability and consistency improvements
- Resolve many cases of duplicate or wrong events
- Correct for fsevents inconsistencies
- Standardize handling of errors and relative paths
- Fix issues with watching
./
- Updated fsevents to 0.3
- Update per-system defaults
- Fix issues with closing chokidar instance
- Fix duplicate change events on win32
- Fixed npm issues related to fsevents dep.
- Updated fsevents to 0.2.
- Optional deps are now truly optional on windows and linux.
- Rewritten in JS, again.
- Fixed some FSEvents-related bugs.
- Added ultra-fast low-CPU OS X file watching with FSEvents. It is enabled by default.
- Added
addDir
andunlinkDir
events. - Polling is now disabled by default on all platforms.
Watcher#close
now also removes all event listeners.
- When
options.ignored
is two-argument function, it will also be called after stating the FS, withstats
argument. unlink
is no longer emitted on directories.
- Added
usePolling
option (default:true
). Whenfalse
, chokidar will usefs.watch
as backend.fs.watch
is much faster, but not like super reliable.
- Fixed watching initially empty directories with
ignoreInitial
option.
- Added node.js 0.10 support.
- File attributes (stat()) are now passed to
add
andchange
events as second arguments. - Changed default polling interval for binary files to 300ms.
- Removed emitting of
change
events beforeunlink
.
- Removed postinstall script to prevent various npm bugs.
- When starting to watch non-existing paths, chokidar will no longer throw ENOENT error.
- Fixed bug with absolute path.
- Added a bunch of new options:
ignoreInitial
that allows to ignore initialadd
events.ignorePermissionErrors
that allows to ignore ENOENT etc perm errors.interval
andbinaryInterval
that allow to change default fs polling intervals.
- Added
all
event that receives two args (event name and path) that combinesadd
,change
andunlink
events. - Switched to
fs.watchFile
on node.js 0.8 on windows. - Files are now correctly unwatched after unlink.
unlink
event are no longer emitted for directories, for consistency withadd
.
- Prevented creating of duplicate 'add' events.
- Fixed a bug when new files in new directories hadn't been added.
- Fixed a bug when unlinked files emitted events after unlink.
- Fixed watching of files on windows.
- Fixed watcher signature.
- Fixed invalid API bug when using
watch()
.
- Rewritten in js.
- Changed api to
chokidar.watch()
. - Fixed compilation on windows.
- Initial release, extracted from Brunch