Error npm test on MacOs Sierra
manuelitox opened this issue · comments
Hey there,
I can't run with success the npm test command:
❯ npm test
> react-scripts test --env=jsdom
Determining test suites to run...2016-10-07 11:38 node[873] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-10-07 11:38 node[873] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:160
throw er; // Unhandled 'error' event
^
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:953:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1400:11)
npm ERR! Test failed. See above for more details.
Environment
Run these commands in the project folder and fill in their results:
npm ls react-scripts:react-scripts@0.6.1node -v:v6.7.0npm -v:3.10.3- Operating system: MacOs Sierra
Any idea?
The issue was fixed to installing of watchman.
Thanks for information! Yeah unfortunately it will likely take some time for the underlying dependencies to fix all Sierra issues.
In case the specificity helps anyone, I ran:
sudo chown -R $(whoami) /usr/localbrew updatebrew install watchman
Haha I just had this issue and your comment fixed it. Thanks!
Another data point: I just had this on Node 6.9.1 but not on 6.3.1.
Installing watchman fixed it as mentioned above. If you get a password prompt enter your password then run all commands again. And if it's not obvious -- close and reopen your terminal or terminal tab after installing.
I had this same issue on node v8.3.0 & OSX v10.12.6 after pulling some changes in my project. However, I'm using yarn v1.0.1. What I've done to fix it is:
rm -rf ./node_modules
yarn cache clean
yarnAfter that running yarn test works as before.
Thank you @Peterlollo !
brew install watchman
worked for me, using high Sierra 10.13.1
well just spent 1.5 hours trying to get the test runner to work. brew install watchman saved the day.
Amazing work on finding that watchman is the case!
But... Is it only me? I feel like we're correcting symptoms ~ shouldn't watchman be
- Included in the create-react-app build process ?
- Mentioned in the documentation that watchman is required to run tests?
I'm not sure this should be closed.
It's not required. The problem is that when it's not available, the alternative watcher doesn't always work and can die unexpectedly. The good news is we're updating to Jest 22 soon which falls back to yet another watcher when watchman isn't available—which doesn't have this issue.
So this should all go away in the next major release.
This is still an issue with node@9.4.0, watchman@4.9.0 macOS@10.13.3 and react-scripts@1.1.1
@villesau still having the same issue as well, watchman doesn't fix the issue either.
I am also still having this issue. node@8.10.0, watchman@4.9.0, macOS@10.13.3, react-scripts@1.1.1
For me at least, it turned out I had an older version of watchman installed globally in npm. Uninstalling that got me working again.
Still having the same issue, installing Watchman didn't help. Any ideas guys ?
I'm currently having this issue. Installing watchman via Brew does eliminate the error, but for some reason Jest can't find my tests so I uninstalled it. I noticed that this problem started as I was making my latest commit, so I tried moving my .git folder out of my project. Lo-and-behold, watching tests works just fine. Moving it back in breaks the tests again.
I got the same error using Travis CI :(
I'm using create-react-app and following instructions here:
Removing jest-enzyme fixed the error for me. I'll try downgrading jest-enzyme to see if it helps.
I'm using create-react-app and following instructions here:
Removing jest-enzyme fixed the error for me. I'll try downgrading jest-enzyme to see if it helps.
Installing worked @afarriaga