--watch Now Throws an Error

[arb]

🐛 Bug Report

I recently updated jest to 24.3.1 and now running with --watch throws an error and does not start. The error is:

2019-03-08 09:51 node[1373] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
Error: Error watching file for changes: EMFILE
    at _errnoException (util.js:1022:11)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1359:9)

I do not have watchman installed globally and again, this was working yesterday and now it's not. I feel like it's an issue with the macOS update but I can't confirm. I know installing watchman via brew is a suggested solution but I've never had to do that before and that seems kind of like it's masking a possible issue with jest.

To Reproduce

npx jest --watch

Expected behavior

I expected jest to continue to work correctly as it has before I updated.

Link to repl or repo (highly encouraged)

https://github.com/arb/celebrate/tree/feature-ref this is the branch I'm working with and currently exhibiting the above behavior.

Run npx envinfo --preset jest

Paste the results here:

npx: installed 1 in 1.538s

  System:
    OS: macOS 10.14.3
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 8.11.1 - ~/.nvm/versions/node/v8.11.1/bin/node
    Yarn: 1.9.4 - ~/.nvm/versions/node/v8.11.1/bin/yarn
    npm: 5.6.0 - ~/.nvm/versions/node/v8.11.1/bin/npm
  npmPackages:
    jest: ^24.3.1 => 24.3.1 

[SimenB]

You can probably install watchman to get around this - brew install watchman.

This is probably because we removed the fsevents crawler (#8048). Not sure why the node crawler explodes, tho.

[arb]

@SimenB I'd rather not do that. Like I said in the initial issue, that seems to be masking an actual issue with jest. If I install watchman, reproducing the problem becomes harder.

[SimenB]

Sure, I was just trying to unblock you

[thymikee]

I tried to run it with yarn (so fresh install) and don't see the error – it's probably related to deps update, so please clean it up. However I can see the same message as here: #8084.

[thymikee]

Closing as duplicate of #8084

[arb]

@thymikee how is this a duplicate of #8084? The error message is completely different and I'm not using the --changedSince flag either.

[thymikee]

This is the error I get when running --watch on your repro, feature-ref branch:

 FAIL   test  test/celebrate.test.js
  ● Test suite failed to run

    TypeError: options.changedFiles.has is not a function

FYI --watch and --changedSince share a lot of logic.

[arb]

I see. Thank you for the clarification! I didn't get that MUCH more specific error when I'm running locally, but I agree, the root cause seems to be the same as #8084.

[SimenB]

Seems this is still an issue for folks

[yoshicarroll]

It is, yes. Jest 23 worked fine. As soon as I updated to Jest 24 24.4.0 it started breaking.