0.7.1 - Limit wait time for file operations

[shawnrushefsky]

• It was previously possible to get stuck in infinite debounce loops. It still is, but only if you explicitly set FILE_WATCHER_MAX_WAIT_MS to 0, or a negative number. Positive values set the maximum amount of time between releasing events.
• This number also applies when waiting for writes to complete, which happens by polling every FILE_WATCHER_STABILITY_CHECK_MS ms.

[Copilot]

Pull Request Overview

This PR introduces a configurable maximum wait time for file watcher operations and bumps the version from 0.7.0 to 0.7.1. The new FILE_WATCHER_MAX_WAIT_MS environment variable (default: 5000ms) ensures that file stability checks and debounced operations will eventually execute even when continuously triggered, preventing indefinite delays.

Key changes:

• Added FILE_WATCHER_MAX_WAIT_MS environment variable to control maximum wait time for file operations
• Enhanced debounceByArg function to track first call times and enforce a maximum wait period
• Updated waitForFileStability to respect the maximum wait timeout

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/files.ts	Implements maxWait logic in both the debouncing mechanism and file stability checking
readme.md	Documents the new FILE_WATCHER_MAX_WAIT_MS environment variable
package.json	Version bump to 0.7.1
package-lock.json	Lockfile version update to 0.7.1

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

🚀 Download the latest release candidate 🚀