Failure to trigger restart on symlink target change

Nodemon monitors file system events to automate application restarts upon file modifications. Documented behavior indicates inconsistent handling of symbolic links across file systems.

When a watched path contains a symlink, changes to the target directory or file may not be observed if the symlink inode or metadata remains unchanged. This creates uncertainty about whether the running application reflects updates made through the linked path.

Does nodemon detect modifications to the contents of a symlink target when the link itself is not modified? Is there a configuration option to force re-evaluation of symlinked directory trees? How is symlink monitoring behavior documented across platforms?