Run tasks whenever watched files change.
JavaScript
#4 Compare This branch is 29 commits ahead, 223 commits behind gruntjs:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
tasks
.gitignore
Gruntfile.js
README.md
package.json

README.md

grunt-watch-nospawn

The Grunt 0.4 release was a major release. One of its plugins, grunt-contrib-watch, was updated for that release but incidentally changed significantly. This module is a drop-in replacement for grunt-contrib-watch designed to retain the same behavior as the branch that was compatible with Grunt 0.3.

It's really only intended to be used by Lineman, but if you've experienced a performance regression with the Grunt 0.4-compatible versions of grunt-contrib-watch, you might consider experimenting with this module.

Why?

We experienced significant performance regressions when upgrading grunt-contrib-watch along with the rest of our grunt plugins. Because our web project tool Lineman relies on rapid feedback upon file change, this regression was a significant impediment to our productivity. The biggest cause performance regression was caused by a change in which the watch task would spawn a new Grunt process for every matched file change. That change's laudable intention was to sandbox tasks from another to prevent any pollution of state in the process. While it succeeds to sandbox the task runs, we haven't experienced related pain in Lineman's workflow and don't think the productivity disruption is worth it.