search

facebook / watchman

Watches files and records, or triggers actions, when they change.
https://facebook.github.io/watchman/
MIT License
12.57k stars 986 forks source link

Watchman fails in case of blank explo cli projects on Win10 #1035

Open cslegany opened 2 years ago

cslegany commented 2 years ago

Expo cli with watchman was fully functional a week ago. Still works in case of older projects where node_modules already exists. In order to duplicate the issue, simply generate a new project using expo cli as:

expo init TinderClone cd .\TinderCone

expo start

Full log: C:\React\ReactNative\TinderClone>expo start --web Starting project at C:\React\ReactNative\TinderClone Developer tools running on http://localhost:19002 Opening developer tools in the browser... Starting Metro Bundler C:\React\ReactNative\TinderClone\node_modules\metro-hermes-compiler\src\emhermesc.js:77 throw ex; ^

Error: connect ENOENT \.\pipe\watchman-CsabaLegány at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1187:16) Emitted 'error' event on Client instance at: at Socket. (C:\React\ReactNative\TinderClone\node_modules\fb-watchman\index.js:118:12) at Socket.emit (node:events:527:28) at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21) { errno: -4058, code: 'ENOENT', syscall: 'connect', address: '\\.\pipe\watchman-CsabaLegány' }

Already tried node update to latest version, watchman reinstall, expo cli update to latest version etc.