Create-react-app: Error npm test on MacOs Sierra

Created on 7 Oct 2016 · 24Comments · Source: facebook/create-react-app

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: [email protected]
node -v: v6.7.0
npm -v: 3.10.3
Operating system: MacOs Sierra

Any idea?

underlying tools

Source

manuelitox

👍19

Most helpful comment

In case the specificity helps anyone, I ran:

sudo chown -R $(whoami) /usr/local
brew update
brew install watchman

Peterlollo on 10 Oct 2016

👍143 ❤32 🎉21 😄9 😕1

All 24 comments

The issue was fixed to installing of watchman.

manuelitox on 7 Oct 2016

👍47 🎉5

Thanks for information! Yeah unfortunately it will likely take some time for the underlying dependencies to fix all Sierra issues.

gaearon on 7 Oct 2016

In case the specificity helps anyone, I ran:

sudo chown -R $(whoami) /usr/local
brew update
brew install watchman

Peterlollo on 10 Oct 2016

👍143 ❤32 🎉21 😄9 😕1

Haha I just had this issue and your comment fixed it. Thanks!

gaearon on 16 Nov 2016

👍11 🎉6

Another data point: I just had this on Node 6.9.1 but not on 6.3.1.

gaearon on 5 Jan 2017

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.

jeff3dx on 11 Aug 2017

👍4

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
yarn

After that running yarn test works as before.

afarriaga on 26 Sep 2017

👎7 👍4

Thank you @Peterlollo !

arcecio on 1 Nov 2017

🎉1

brew install watchman

worked for me, using high Sierra 10.13.1

packetstracer on 23 Nov 2017

👍9

well just spent 1.5 hours trying to get the test runner to work. brew install watchman saved the day.

mgan59 on 24 Nov 2017

👍3

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

1) Included in the create-react-app build process ?
2) Mentioned in the documentation that watchman is required to run tests?

I'm not sure this should be closed.

etiennejcharles on 9 Jan 2018

👍6

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.

gaearon on 10 Jan 2018

So this should all go away in the next major release.

gaearon on 10 Jan 2018

👍9

This is still an issue with [email protected], [email protected] [email protected] and [email protected]

villesau on 13 Mar 2018

@villesau still having the same issue as well, watchman doesn't fix the issue either.

eddieduro on 17 Mar 2018

I am also still having this issue. [email protected], [email protected], [email protected], [email protected]

andrewtpoe on 21 Mar 2018

For me at least, it turned out I had an older version of watchman installed globally in npm. Uninstalling that got me working again.

andrewtpoe on 21 Mar 2018

👍1

Still having the same issue, installing Watchman didn't help. Any ideas guys ?

maciekgrzybek on 27 Mar 2018

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.