gruntjs/grunt-contrib-watch

Run tasks whenever watched files change.

Hosted by OpenJS Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

gruntjs/grunt-contrib-watch has 1.5k+ stars and 350+ forks on GitHub, is written in JavaScript, and was last pushed on Mar 29, 2023. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Plugin / ExtensionCategory(s):Build Systems & Package ManagersDeveloper Tools
Added to GitGenius on October 15th, 2026
Created on September 17th, 2012
Open Issues & Pull Requests: 125 (+0)
GitHub issues: Enabled
Number of forks: 354
Total Stargazers: 1,959 (+0)
Total Subscribers: 51 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 53.3 days
Mean response time: 94.5 days
90th percentile: 236.6 days
Tracked items: 4

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 250 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

grunt-contrib-watch is a Grunt plugin that runs predefined tasks whenever watched file patterns are added, changed, or deleted.

The tool solves the problem of manually re-running build tasks during development by monitoring specified file patterns and automatically triggering configured Grunt tasks when those files change. It uses file system watching to detect modifications and can be configured to run different tasks based on the type of event (added, changed, or deleted) and which files match the watched patterns.

Developers should choose this tool if they are already using Grunt as their task runner and want to automate task execution during development. It suits projects where rapid feedback during editing is valuable, such as when compiling assets, running tests, or linting code. The tool offers several configuration options to tune behavior: the spawn option controls whether tasks run in child processes, with spawning disabled providing faster reaction times at the cost of stability; the interrupt option determines whether new file changes should terminate ongoing task runs or wait for completion; and the debounceDelay option prevents rapid successive triggers for the same file. The event option lets you filter which types of file changes trigger tasks, and the reload option can restart the watch task itself when configuration files change.

The project maintains active test coverage across multiple platforms and accepts community contributions through established processes.