Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readme backend uses unclear #136

Open
wighawag opened this issue Mar 23, 2023 · 1 comment
Open

readme backend uses unclear #136

wighawag opened this issue Mar 23, 2023 · 1 comment

Comments

@wighawag
Copy link

Hi, in the doc there is both these sentences :

@parcel/watcher has the following watcher backends, listed in priority order:

FSEvents on macOS
Watchman if installed
inotify on Linux
ReadDirectoryChangesW on Windows

and

@parcel/watcher has the following watcher backends, listed in priority order:

FSEvents on macOS
Watchman if installed
fts (brute force) on Linux
FindFirstFile (brute force) on Windows

The are listed in 2 different sections, one for watching, one for querying but the wording make me wonder if I should worry about this if I intent to use the watcher to watch file like I do with chokidar

Not really interested in the watchman option as I do not expect all the user of my tool to want to install it
so my worry is on Linux.

Basically should I use chokidar or @parcel/watcher ?

@mischnic
Copy link
Member

For watching (so to listen for file changes while your tool is running), macOS, Linux and Windows all have some native backend that works fine. Even without watchman.

But for querying (so to answer "which files changed since you last ran you tool"), there's only a native backend on macOS and all other platforms use bruteforce or Watchman if available.

So you should be fine as far as I understand you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants