watchman : unknown option --no-pretty error while npm start
See original GitHub issueHi I am getting ‘unknown option --no-pretty’ error while trying to start development server of react-native android project.
I executed
npm start
Then i got this:
React packager ready.
ERROR: Unknown option --no-pretty
Watchman: watchman--no-pretty get-sockname returned with exit code 1 ERROR: Unknown option --no-pretty
ERROR watchman--no-pretty get-sockname returned with exit code 1 ERROR: Unknown option --no-pretty
Error: watchman--no-pretty get-sockname returned with exit code 1 ERROR: Unknown option --no-pretty
at ChildProcess.<anonymous> (/home/sreejith/projects/sample/node_modules/react-native/node_modules/sane/node_modules/fb-watchman/index.js:194:18)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:817:16)
at Socket.<anonymous> (internal/child_process.js:319:11)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:469:12)
Please help
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:44 (3 by maintainers)
Top Results From Across the Web
unable to run npm start for react-native project - Stack Overflow
Try reinstalling watchman: npm r -g watchman brew update && brew upgrade brew install watchman. If that doesn't fix it, try the answers...
Read more >chandu0101/sri - Gitter
Sign in to start talking ... npm fun: Watchman: watchman--no-pretty get-sockname returned with exit code 1 ERROR: Unknown option --no-pretty.
Read more >watchman crawl failed. retrying once with node crawler. react ...
Wez Furlong's answer worked for me, but I had to provide full disk access to watchman in order to run watchman watch-project command...
Read more >watchman--no-pretty get-sockname returned with exit code 1 ...
React packager ready. ERROR: Unknown option –no-pretty. Watchman: watchman–no-pretty get-sockname returned with exit code 1 ERROR: Unknown ...
Read more >webpack-dev-server - npm
Start using webpack-dev-server in your project by running `npm i ... Following options are available with webpack serve :
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
ok i fixed it this way: npm r -g watchman brew update && brew upgrade brew install watchman
I have just solved an issue similar to this one by running
$ sudo chown -R $(whoami):admin /usr/local
I must have messed with the permissions at one point or the other. Hope it helps!