Consider using `fs.watch` for file watching

[tsmaeder]

Feature Description:

In node 19, recursive file watching was added to the nodejs file watching API. (see https://nodejs.org/docs/latest/api/fs.html#fswatchfilename-options-listener). We should consider using this API instead of the parcel watcher.

[tsmaeder]

Depends on #15857

[JonasHelming]

I find this interesting, as I believe we still might have some issues with file watching. @ndoschek

[Niklas-Dahlquist]

This upgrade would solve the issue experienced on Windows11, see this discussion on parcel watcher
parcel-bundler/watcher#155

[tsmaeder]

@Niklas-Dahlquist IMO the biggest advantage would be to have a general purpose, actively developed implementation. NSFW is not really active and the Parcel watcher is, well, for Parcel, not general consumption.

[rschnekenbu]

I have the same findings here on my side, working on the popup window effect (#14890).

The current issue on Windows is that Watchman (one of the potential backend for parcel/watcher library) may not be found. In order to be found, The watchman backend tries to connect with https://github.com/parcel-bundler/watcher/blob/1ca032aa8339260a8a3bcf825c3a1a71e3e43542/src/watchman/WatchmanBackend.cc#L68. The getSockPath implementation currently relies on windows on this: popen("watchman --output-encoding=bser get-sockname 2>/dev/null", "r");
This leads to that error message and the forementionned console window to popup.

It is possible to set the backend to another default one on windows, which is slower, but that does not cause an error on startup and so no popup window. As watchman is not found, we can safely assume that on windows, the slower backend is used in any case as a backup. So that should not impact performances.

There were some long discussion on using parcel or other file watching library here: vitejs/vite#13593