watchr
Advanced tools
Changelog
v2.6.0 2016 July 15
Readme
Better file system watching for Node.js
npm install --save watchrwatchrrequire('watchr')This package is published with the following editions:
watchr/src/lib/getmac.coffee is Source + CoffeeScript + Requirewatchr/es5/lib/getmac.js is CoffeeScript Compiled JavaScript + ES5 + RequireWatchr provides a normalised API the file watching APIs of different node versions, nested/recursive file and directory watching, and accurate detailed events for file/directory creations, updates, and deletions.
You install it via npm install watchr and use it via require('watchr').watch(config). Available configuration options are:
path a single path to watchpaths an array of paths to watchlistener a single change listener to fire when a change occurslisteners an array of listeners to fire when a change occurs, overloaded to accept the following values:
changeListener a single change listener[changeListener] an array of change listeners{eventName: eventListener} an object keyed with the event names and valued with a single event listener{eventName: [eventListener]} an object keyed with the event names and valued with an array of event listenersnext (optional, defaults to null) a completion callback to fire once the watchers have been setup, arguments are:
path configuration option: err, watcherInstancepaths configuration option: err, [watcherInstance,...]stat (optional, defaults to null) a file stat object to use for the path, instead of fetching a new oneinterval (optional, defaults to 5007) for systems that poll to detect file changes, how often should it poll in millsecondspersistent (optional, defaults to true) whether or not we should keep the node process alive for as long as files are still being watchedcatchupDelay (optional, defaults to 2000) because swap files delete the original file, then rename a temporary file over-top of the original file, to ensure the change is reported correctly we must have a delay in place that waits until all change events for that file have finished, before starting the detection of what changedpreferredMethods (optional, defaults to ['watch','watchFile']) which order should we prefer our watching methods to be tried?followLinks (optional, defaults to true) follow symlinks, i.e. use stat rather than lstatignorePaths (optional, defaults to false) an array of full paths to ignoreignoreHiddenFiles (optional, defaults to false) whether or not to ignored files which filename starts with a .ignoreCommonPatterns (optional, defaults to true) whether or not to ignore common undesirable file patterns (e.g. .svn, .git, .DS_Store, thumbs.db, etc)ignoreCustomPatterns (optional, defaults to null) any custom ignore patterns that you would also like to ignore along with the common patternsThe following events are available to your via the listeners:
log for debugging, receives the arguments logLevel ,args...error for gracefully listening to error events, receives the arguments err
watching for when watching of the path has completed, receives the arguments err, isWatchingchange for listening to change events, receives the arguments changeType, fullPath, currentStat, previousStat, received arguments will be:
'update', fullPath, currentStat, previousStat'create', fullPath, currentStat, null'delete', fullPath, null, previousStatTo wrap it all together, it would look like this:
// Require
var watchr = require('watchr')
// Watch a directory or file
console.log('Watch our paths')
watchr.watch({
paths: ['path1', 'path2', 'path3'],
listeners: {
log: function (logLevel) {
console.log('a log message occured:', arguments)
},
error: function (err) {
console.log('an error occured:', err)
},
watching: function (err, watcherInstance, isWatching){
if (err) {
console.log("watching the path " + watcherInstance.path + " failed with error", err)
} else {
console.log("watching the path " + watcherInstance.path + " completed")
}
},
change: function(changeType, filePath, fileCurrentStat, filePreviousStat){
console.log('a change event occured:', arguments)
}
},
next: function(err, watchers){
if (err) {
return console.log("watching everything failed with error", err)
} else {
console.log('watching everything completed', watchers)
}
// Close watchers after 60 seconds
setTimeout(function () {
console.log('Stop watching our paths')
for ( var i = 0; i < watchers.length; i++ ) {
watchers[i].close()
}
}, 60 * 1000)
}
})
You can test the above code snippet by running the following:
npm install -g watchr
watchr
Discover the release history by heading on over to the HISTORY.md file.
Discover how you can contribute by heading on over to the CONTRIBUTING.md file.
These amazing people are maintaining this project:
No sponsors yet! Will you be the first?
These amazing people have contributed code to this project:
Discover how you can contribute by heading on over to the CONTRIBUTING.md file.
Unless stated otherwise all works are:
and licensed under:
FAQs
Better file system watching for Node.js
We found that watchr demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Researchers recently demonstrated that the npm Registry is vulnerable to cache poisoning combined with DoS, posing significant risks for package availability.
Security News
The June TC39 meeting wrapped up this week with eight proposals moving on to the next stage. Here's a quick roundup of the features that the committee approved to advance.
Security News
Cyber extortion in the US and Canada hit record levels in 2023, with ransomware attacks surging and median ransom demands skyrocketing, though fewer companies are choosing to pay ransoms.