Skip to content

Latest commit

 

History

History
187 lines (149 loc) · 8.72 KB

HISTORY.md

File metadata and controls

187 lines (149 loc) · 8.72 KB
Raw

History

v2.4.13 February 7, 2015

  • Updated dependencies

v2.4.12 December 17, 2014

v2.4.11 February 7, 2014

  • Fixed interval option not beeing passed on to child watchers (regression since v2.4.7)

v2.4.10 February 7, 2014

v2.4.9 January 28, 2014

  • Fixed "me" is undefined errors (regression since v2.4.7)

v2.4.8 December 30, 2013

  • You can now pass falsey values forcatchupDelay to disable it

v2.4.7 December 19, 2013

v2.4.6 November 18, 2013

  • Updated dependencies

v2.4.5 November 17, 2013

  • Updated dependencies

v2.4.4 October 10, 2013

  • Added the ability to turn off following links by setting followLinks to false
  • Prefer accuracy over speed
    • Use the watch method by default, but don't trust it at all, always double check everything

v2.4.3 April 10, 2013

  • More work on swap file handling

v2.4.2 April 10, 2013

  • File copies will now trigger events throughout the copy rather than just at the start of the copy

v2.4.1 April 10, 2013

  • Fixed bubblr events
  • Fixed swap file detection

v2.4.0 April 5, 2013

  • Updated dependencies

v2.3.10 April 1, 2013

  • Updated dependencies

v2.3.9 March 17, 2013

  • Made it so if duplicateDelay is falsey we will not do a duplicate check

v2.3.8 March 17, 2013

v2.3.7 February 6, 2013

  • Changed the preferredMethod option into preferredMethods which accepts an array, defaults to ['watch','watchFile']
  • If the watch action fails at the eve level we will try again with the preferredMethods reversed
    • This solves issue #31 where watching of large files would fail
  • Changed the interval option to default to 5007 (recommended by node) instead of 100 as it was before
    • The watch method provides us with immediate notification of changes without utilising polling, however the watch method fails for large amounts of files, in which case we will fall back to the watchFile method that will use this option, if the option is too small we will be constantly polling the large amount of files for changes using up all the CPU and memory, hence the change into a larger increment which has no CPU and memory impact.

v2.3.6 February 6, 2013

  • Fixed fallback when preferredMethod is watchFile

v2.3.5 February 6, 2013

  • Fixed uncaught exceptions when intialising watchers under certain circumstances

v2.3.4 February 5, 2013

  • Better handling and detection of failed watching operations
  • Better handling of duplicated events
  • Watching is now an atomic operation
    • If watching fails for a descendant, we will close everything related to that watch operation of the eve
  • We now prefer the watch method over the watchFile method
    • This offers great reliability and way less CPU and memory foot print
    • If you still wish to prefer watchFile, then set the new configuration option preferredMethod to watchFile
  • Closes issue #30 thanks to Howard Tyson

v2.3.3 January 8, 2013

v2.3.2 January 6, 2013

v2.3.1 December 19, 2012

v2.3.0 December 17, 2012

  • This is a backwards compatiblity break, however updating is easy, read the notes below.
  • We've updated the events we emit to be:
    • log for debugging, receives the arguments logLevel ,args...
    • watching for when watching of the path has completed, receives the arguments err, isWatching
    • change for listening to change events, receives the arguments changeType, fullPath, currentStat, previousStat
    • error for gracefully listening to error events, receives the arguments err
    • read the README to learn how to bind to these new events
  • The changeType argument for change listeners has been changed for better clarity and consitency:
    • change is now update
    • new is now create
    • unlink is now delete
  • We've updated the return arguments for require('watchr').watch for better consitency:
    • if you send the paths option, you will receive the arguments err, results where results is an array of watcher instances
    • if you send the path option, you receive the arguments err, watcherInstance

v2.2.1 December 16, 2012

  • Fixed sub directory scans ignoring our ignore patterns
  • Updated dependencies

v2.2.0 December 15, 2012

v2.1.6 November 6, 2012

v2.1.5 September 29, 2012

  • Fixed completion callback not firing when trying to watch a path that doesn't exist

v2.1.4 September 27, 2012

  • Fixed new listeners not being added for directories that have already been watched
  • Fixed completion callbacks happening too soon
  • Thanks to pull request #14 by Casey Foster

v2.1.3 August 10, 2012

  • Re-added markdown files to npm distribution as they are required for the npm website

v2.1.2 July 7, 2012

  • Fixed spelling of persistent
  • Explicitly set the defaults for the options ignoreHiddenFiles and ignorePatterns

v2.1.1 July 7, 2012

  • Added support for interval and persistant options
  • Improved unlink detection
  • Optimised unlink handling

v2.1.0 June 22, 2012

  • watchr.watchr changes
    • now only accepts one argument which is an object
    • added new paths property which is an array of multiple paths to watch
    • will only watch paths that actually exist (before it use to throw an error)
  • Fixed a few bugs
  • Added support for node v0.7/v0.8
  • Moved tests from Mocha to Joe

v2.0.3 April 19, 2012

  • Fixed a bug with closing watchers
  • Now requires pre-compiled code

v2.0.0 April 19, 2012

  • Big rewrite
  • Got rid of the delay
  • Now always fires events
  • Watcher instsances inherit from Node's EventEmitter
  • Events for change, unlink and new

v1.0.0 February 11, 2012

  • Better support for ignoring hidden files
  • Improved documentation, readme
  • Added History.md file
  • Added unit tests using Mocha

v0.1.0 Nov 13, 2012

  • Initial working version