You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On macOS, when the option usePolling is set to true, useFsEvents is set to false (as a side effect).
When the env variable CHOKIDAR_USEPOLLING=1 is set, it sets usePolling to true, but leaves useFsEvents as true.
Currently, I'm running into an issue in gatsby's source-filesystem plugin in how chokidar deals with hard links. I specifically need usePolling to be true and useFsEvents to be false. (See gatsbyjs/gatsby#36877 and gatsbyjs/gatsby#36975)
The easiest solution would be to add a CHOKIDAR_USEFSEVENTS env variable so I can correctly emulate the behavior when using the options.
Another option would be to mimic the options behavior (usePolling=true, useFsEvents=false) when using the env variable. The danger here would be anyone using the existing behavior.
If I can get some direction on which direction is better I can submit a PR that does it.
The text was updated successfully, but these errors were encountered:
Another option would be to mimic the options behavior (usePolling=true, useFsEvents=false) when using the env variable. The danger here would be anyone using the existing behavior.
On macOS, when the option
usePolling
is set to true,useFsEvents
is set to false (as a side effect).When the env variable
CHOKIDAR_USEPOLLING=1
is set, it setsusePolling
to true, but leavesuseFsEvents
as true.Currently, I'm running into an issue in gatsby's source-filesystem plugin in how chokidar deals with hard links. I specifically need
usePolling
to be true anduseFsEvents
to be false. (See gatsbyjs/gatsby#36877 and gatsbyjs/gatsby#36975)The easiest solution would be to add a CHOKIDAR_USEFSEVENTS env variable so I can correctly emulate the behavior when using the options.
Another option would be to mimic the options behavior (
usePolling=true, useFsEvents=false
) when using the env variable. The danger here would be anyone using the existing behavior.If I can get some direction on which direction is better I can submit a PR that does it.
The text was updated successfully, but these errors were encountered: