actually working file tree watching library
Watch for changes in a file tree. I wrote this because in my search for an actually reliable/working watcher library on npm, I kept coming up short. This implementation is brief and accomplishes its goal reliably.
File/directory watching in node.js is notoriously bad. For example:
fs.watch()when used on a directory, might not tell you what file changed. Just that "something" in the directory changed. Depending on the platform. Useless.
- If you're lucky enough to get a filename from
fs.watch(), you're in the dark on whether that file is actually a directory. Or any other details on the file in question. Useless.
fs.watch()does not detect adds, removes, or updates specifically. Just "change". Useless.
fs.watch()when used on a directory, only watches one level deep. It's up to you to create more watch instances for subdirectories. Useless.
fs.watchFile(), the alternative to
fs.watch(), when used on a directory, doesn't give you the filename of the change either. Also it uses polling which is obviously hacky and defeats the goal of an evented watcher. Useless.
Moreover, npm-level watching libraries that attempt to remedy the above have annoying caveats, such as:
- Events aren't emitted in some cases, especially relating to subdirectories
- Events are duplicated in some cases (
fs.watch()is also guilty of this)
- Poor error handling such as not accounting for ENOFILE (race condition from deletion) or EMFILE (large directory trees)
- Deletes of directories poorly handled -- you might get notified that a directory was deleted, but not notified of each file in that directory
- Lack of node 0.10 support
- May require you to add files, directories, or patterns manually to the watcher
- Getting fancy with globs/filters, when the best separation of concerns is for a watching library to just watch and tell you the filename and what happened.
- Wonky APIs which try to reinvent
fs.Statsor are generally over-engineered
- Lack of documentation or commitment from author
- Being written in, ahem, coffee-script
- Et cetera!
saw takes a very simple and reliable approach which consists of:
- Recursing through the directory given
fs.watch()to all newly detected files
fs.Statsinstances for all files
- Comparing the file tree with the last scan (if available) and emitting events based on the difference
- Performing steps 1-4 on the changed dir (or parent of the changed file) when
fs.watch()triggers an event.
var saw = ;// to unwatch all files, call close():
- You can also pass a glob pattern or array of glob patterns as the first argument.
- You can omit the first argument to watch the current working directory.
fileobject is the same as returned by readdirp.
cwd(String, default: first argument or
process.cwd()if first argument isn't a directory), the directory to consider as root for relative paths.
true), whether or not to keep the process open when watching is active.
false), whether or not to watch dotfiles.
cache(Object), options to pass to lru-cache.
Terra Eclipse, Inc. is a nationally recognized political technology and strategy firm located in Aptos, CA and Washington, D.C.
- Copyright (C) 2013-14 Carlos Rodriguez (http://s8f.org/)
- Copyright (C) 2013-14 Terra Eclipse, Inc. (http://www.terraeclipse.com/)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.