Unresolved behavior of nodemon’s batch restart logic on rapid file changes

Goal

Determine how nodemon handles successive file changes that occur in quick succession. The objective is to understand whether nodemon restarts the application once per detected batch or after each individual change, and how the built‑in debounce mechanism influences this.

Context and Constraints

• Rapid edits trigger multiple file‑watch events before nodemon can process them.
• The --delay option is available to introduce a pause, but its effect on batching is unclear.
• Operating‑system differences in the underlying file‑watcher may affect event grouping.

Unresolved Questions

1. Does nodemon coalesce rapid file changes into a single restart per batch, or does it restart after each change?
2. How does the --delay flag influence this batching behavior?
3. Are there OS‑specific differences in how nodemon groups rapid changes?