René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"--watch should monitor replaced files","articleBody":"### What is the problem this feature will solve?\r\n\r\nCurrently, `--watch` watches an [inode](https://nodejs.org/docs/latest/api/fs.html#inodes) and not necessarily what the user might consider a \"file\". This can cause confusion on systems that write to disk by deleting the old file and then creating a new one.\r\n\r\nFor example, when using Docker Compose's [`watch`](https://docs.docker.com/compose/file-watch/) mode, the watched file is first deleted.  When a new file is created Node currently fails to restart on file changes, as  node is still watching the inode of the deleted file, and doesn't react to the new file being created.\r\n\r\n### What is the feature you are proposing to solve the problem?\r\n\r\nWhile this behavior makes sense for the lower-level and more \"raw\" `fs.watch()`, perhaps the more general `--watch` behavior can be expanded to be smarter about detecting replaced files. Alternatively, a new flag can be introduced with this behavior.\r\n\r\n### What alternatives have you considered?\r\n\r\nOther alternatives require using one of the different file watcher libs. That seems like a step down from the otherwise awesome native `watch` feature.\r\n\r\n\r\nDocker Compose Issue: [[BUG] Compose Watch With “node –watch” Only Reloads First Time](https://github.com/docker/compose/issues/11090)\r\nDocker Issue: [node --watch doesn't work well within a container](https://github.com/moby/moby/issues/47061)","author":{"url":"https://github.com/mbrevda","@type":"Person","name":"mbrevda"},"datePublished":"2024-01-31T17:07:56Z","url":"https://github.com/nodejs/node/issues/51621"}