Go to file
2013-01-09 12:30:57 -08:00
docs Add FAQ about use with Grunt v0.3. Make FAQs appear again. 2013-01-02 13:35:42 -08:00
tasks Use grunt.file.expand to support exclusions. Closes GH-30. 2012-12-21 16:22:40 -08:00
test Tighten up tests 2012-12-13 19:18:37 -08:00
.editorconfig Add .editorconfig file 2012-11-28 11:19:55 -08:00
.gitattributes prep for upcoming grunt release. Closes GH-23. 2012-12-13 16:09:16 -08:00
.gitignore first commit 2012-09-17 16:01:19 -05:00
.jshintrc Updates to run on Grunt v0.4 2012-10-09 15:10:58 -07:00
.travis.yml Install grunt-cli in travis before_script instead of as devDep 2012-11-28 11:11:50 -08:00
AUTHORS prep for upcoming grunt release. Closes GH-23. 2012-12-13 16:09:16 -08:00
CHANGELOG Update to show compatibility with grunt@0.4.0rc5. Publishing as 0.2.0rc5. 2013-01-09 12:30:57 -08:00
CONTRIBUTING.md Run nodeunit instead of test. Use the latest deps. 2012-11-19 13:06:25 -08:00
Gruntfile.js Tighten up tests 2012-12-13 19:18:37 -08:00
LICENSE-MIT prep for upcoming grunt release. Closes GH-23. 2012-12-13 16:09:16 -08:00
package.json Update to show compatibility with grunt@0.4.0rc5. Publishing as 0.2.0rc5. 2013-01-09 12:30:57 -08:00
README.md Update to show compatibility with grunt@0.4.0rc5. Publishing as 0.2.0rc5. 2013-01-09 12:30:57 -08:00

grunt-contrib-watch Build Status

Run predefined tasks whenever watched file patterns are added, changed or deleted.

Getting Started

If you haven't used grunt before, be sure to check out the Getting Started guide, as it explains how to create a gruntfile as well as install and use grunt plugins. Once you're familiar with that process, install this plugin with this command:

npm install grunt-contrib-watch --save-dev

Watch task

Run this task with the grunt watch command.

Overview

Inside your Gruntfile.js file, add a section named watch. This section specifies the files to watch, tasks to run when an event occurs and the options used.

Settings

There are a number of options available. Please review the minimatch options here. As well as some additional options as follows:

files

Type: String|Array

This defines what file patterns this task will watch. Can be a string or an array of files and/or minimatch patterns.

tasks

Type: String|Array

This defines which tasks to run when a watched file event occurs.

options.interrupt

Type: boolean Default: false

As files are modified this watch task will spawn tasks in child processes. The default behavior will only spawn a new child process per target when the previous process has finished. Set the interrupt option to true to terminate the previous process and spawn a new one upon later changes.

Example:

watch: {
  scripts: {
    files: '**/*.js',
    tasks: ['jshint'],
    options: {
      interrupt: true
    }
  }
}

options.debounceDelay

Type: Integer Default: 500

How long to wait before emitting events in succession for the same filepath and status. For example if your Gruntfile.js file was changed, a changed event will only fire again after the given milliseconds.

Example:

watch: {
  scripts: {
    files: '**/*.js',
    tasks: ['jshint'],
    options: {
      debounceDelay: 250
    }
  }
}

options.interval

Type: Integer Default: 100

The interval is passed to fs.watchFile. Since interval is only used by fs.watchFile and this watcher also uses fs.watch; it is recommended to ignore this option. Default is 100ms.

Examples

// Simple config to run jshint any time a file is added, changed or deleted
grunt.initConfig({
  watch: {
    files: '**/*',
    tasks: ['jshint']
  }
});
// Advanced config. Run specific tasks when specific files are added, changed or deleted.
grunt.initConfig({
  watch: {
    gruntfile: {
      files: 'Gruntfile.js',
      tasks: ['jshint:gruntfile'],
      options: {
        nocase: true
      }
    },
    src: {
      files: ['lib/*.js', 'css/**/*.scss', '!lib/dontwatch.js'],
      tasks: ['default']
    },
    test: {
      files: '<%= jshint.test.src %>',
      tasks: ['jshint:test', 'qunit']
    }
  }
});

FAQs

How do I fix the error EMFILE: Too many opened files.?

This is because of your system's max opened file limit. For OSX the default is very low (256). Temporarily increase your limit with ulimit -n 10480, the number being the new max limit.

Can I use this with Grunt v0.3?

Yes. Although grunt-contrib-watch is a replacement watch task for Grunt v0.4, version grunt-contrib-watch@0.1.x is compatible with Grunt v0.3. grunt-contrib-watch >= 0.2.x is *only compatible and recommended to use with Grunt v0.4.

Release History

  • 2013-01-08v0.2.0rc5Updating to work with grunt v0.4.0rc5.
  • 2012-12-14v0.2.0aConversion to grunt v0.4 conventions. Remove node v0.6 and grunt v0.3 support. Allow watch task to be renamed. Use grunt.util.spawn "grunt" option. Updated to gaze@0.3.0, forceWatchMethod option removed.
  • 2012-10-31v0.1.4Prevent watch from spawning duplicate watch tasks
  • 2012-10-27v0.1.3Better method to spawn the grunt bin Bump gaze to v0.2.0. Better handles some events and new option forceWatchMethod Only support Node.js >= v0.8
  • 2012-10-16v0.1.2Only spawn a process per task one at a time Add interrupt option to cancel previous spawned process Grunt v0.3 compatibility changes
  • 2012-10-15v0.1.1Fallback to global grunt bin if local doesnt exist. Fatal if bin cannot be found Update to gaze 0.1.6
  • 2012-10-07v0.1.0Release watch task Remove spawn from helper Run on Grunt v0.4

Task submitted by Kyle Robinson Young

This file was generated on Wed Jan 09 2013 12:29:30.