WebStorm File Watchers Not Triggering on Save: Diagnostic Guide

File Watcher silent after save

A File Watcher in WebStorm is configured to run an external tool when a source file is saved. The recognizable failure is no execution at all: saving a file inside the project produces no entry in the File Watcher tool window, no console output, and no generated output file. The useful takeaway is that WebStorm will suppress or skip watchers when the watcher is disabled, the file is outside scope, Power Save Mode blocks file system events, or the output path is excluded.

Cause, symptom and quick check

Ordered checks

1. Open Settings → Tools → File Watchers. Confirm the watcher is enabled. Verify Scope matches the file you are saving. Scope is a WebStorm filter that limits which files trigger the watcher. An overly narrow scope causes silent misses.

2. Verify Power Save Mode is disabled. Settings → Appearance & Behavior → System Settings → Power Save Mode. When on, WebStorm deliberately blocks file system event listeners to reduce CPU use.

3. Check output exclusions. Settings → Editor → File Types → Ignore files and folders. If the output directory or file pattern is listed, WebStorm will not report changes and may suppress watcher runs.

4. Review the File Watcher tool window. View → Tool Windows → File Watcher. Look for error messages, skipped runs, or “file is excluded” notes after a save.

5. Inspect IDE logs. Help → Diagnostic Tools → Show Log in Explorer. Open the latest idea.log and search for FileWatcher. Exceptions here indicate plugin or JVM problems rather than configuration.

Fixes tied to findings

Watcher disabled or scope mismatch

Enable the watcher and adjust Scope to include the file. Example scope for a TypeScript project: file:*.ts with a directory filter limited to src/. Avoid broad patterns like **/* as they increase IDE load and event processing.

Power Save Mode on

Turn Power Save Mode off. This restores file system event handling. Note that disabling Power Save Mode may increase CPU usage and reduce battery life on laptops.

Output excluded

Remove the output path from Ignore files and folders, or change the watcher output location to a non-excluded directory. After change, save a file in scope and confirm the output file is generated or modified as defined.

Plugin or IDE errors in log

Update the relevant plugin, e.g., NodeJS or TypeScript, and update WebStorm to the latest patch. If logs show repeated OutOfMemory errors, increase IDE heap via Help → Edit Custom VM Options. Add or edit -Xmx2g as a placeholder value appropriate to your machine, then restart WebStorm. Changing VM options modifies IDE runtime memory.

Verification after change

• Save a file within the watcher scope and observe the File Watcher tool window for immediate execution and expected output.
• Confirm the output file specified in the watcher settings is generated or modified.
• Enable FINE-level logging via Help → Diagnostic Tools → Debug Log Settings and ensure no FileWatcher-related errors appear in the IDE log after the test.

When to escalate

Escalate to JetBrains support when:

• The watcher remains inactive after applying all fixes and logs show internal exceptions.
• The issue reproduces on a fresh IDE configuration with no plugins.
• The problem persists across multiple WebStorm versions, e.g., 2024.3 and 2025.1, indicating a possible regression.

Limitations and cautions

File Watchers rely on local file system events. Network drives, WSL mounts, or Docker volumes may deliver events inconsistently. Scope patterns are evaluated per save; changes to scope require a project reopen to take full effect in some cases. Setting watcher Scope to overly broad patterns can cause significant IDE performance degradation.