macOS `fsevents unavailable (this watcher can only be used on Darwin)`

Question

macOS `fsevents unavailable (this watcher can only be used on Darwin)`

Glutnix opened this issue 6 years ago · 39 comments

Glutnix commented 6 years ago

Environment

code -v : 1.31.0 7c66f58312b48ed8ca4e387ebd9ffe9605332caa x64
node -v: 10.15.1
npm -v: 6.7.0
npm ls jest or npm ls react-scripts (if you haven’t ejected): jest@24.0.0
your vscode-jest settings if customized:
- jest.pathToJest? blank
- jest.pathToConfig? blank
- was working before upgrading VScode to 1.31.0
Operating system: macOS 10.14.3

Prerequisite

are you able to run jest test from command line? yes
how do you run your tests from command line? (for example: npm run test or node_modules/.bin/jest):
- npm run test, which is just a shortcut to jest .

Steps to Reproduce

Have Jest Extension installed into older VSCode
Upgrade VSCode to 1.31.1
Open a test/spec file

Relevant Debug Info

Error: `fsevents` unavailable (this watcher can only be used on Darwin)
    at new FSEventsWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/sane/src/fsevents_watcher.js:37:13)
    at createWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:952:23)
    at Array.map (<anonymous>)
    at HasteMap._watch (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:1127:44)
    at _buildPromise._buildFileMap.then.then.hasteMap (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:441:23)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

Error: `fsevents` unavailable (this watcher can only be used on Darwin)
    at new FSEventsWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/sane/src/fsevents_watcher.js:37:13)
    at createWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:952:23)
    at Array.map (<anonymous>)
    at HasteMap._watch (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:1127:44)
    at _buildPromise._buildFileMap.then.then.hasteMap (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:441:23)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

Error: `fsevents` unavailable (this watcher can only be used on Darwin)
    at new FSEventsWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/sane/src/fsevents_watcher.js:37:13)
    at createWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:952:23)
    at Array.map (<anonymous>)
    at HasteMap._watch (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:1127:44)
    at _buildPromise._buildFileMap.then.then.hasteMap (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:441:23)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

Error: `fsevents` unavailable (this watcher can only be used on Darwin)
    at new FSEventsWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/sane/src/fsevents_watcher.js:37:13)
    at createWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:952:23)
    at Array.map (<anonymous>)
    at HasteMap._watch (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:1127:44)
    at _buildPromise._buildFileMap.then.then.hasteMap (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:441:23)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

Error: `fsevents` unavailable (this watcher can only be used on Darwin)
    at new FSEventsWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/sane/src/fsevents_watcher.js:37:13)
    at createWatcher (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:952:23)
    at Array.map (<anonymous>)
    at HasteMap._watch (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:1127:44)
    at _buildPromise._buildFileMap.then.then.hasteMap (/Users/btaylor/Sites/nzta-seatbelts/node_modules/jest-haste-map/build/index.js:441:23)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

Starting Jest in Watch mode failed too many times and has been stopped.
 see troubleshooting: https://github.com/jest-community/vscode-jest/blob/master/README.md#troubleshooting

Expected Behavior

Watch mode to work as expected

Actual Behavior

A notification is shown "Starting Jest in Watch mode failed too many times and has been stopped." and the Jest extension output window is shown with the debug info above.

Answer 1 · 2019-02-08T13:00:14.000Z

It happens in version 1.31.0 as well. I see that you have 1.31.1 listed. Is that the Insiders version?

Answer 2 · 2019-02-08T19:19:44.000Z

No, 1.31.1 was just the latest vscode release

Answer 3 · 2019-02-11T09:16:23.000Z

brew install watchman fixed the problem for me.

cm-pliser-tdd-by-example/tdd-by-example-js#10 (comment)

Answer 4 · 2019-02-12T23:01:37.000Z

I had watchman already installed. I did a full brew reinstall watchman and still no dice.

Answer 5 · 2019-02-13T20:38:41.000Z

@EdouardBougon Those instructions worked for me, thanks!

Answer 6 · 2019-02-20T02:12:36.000Z

Figured it out. I didn't realise that Nuxt was putting a jest config into package.json, and for some reason, I had "watchman": false in there.. sigh 😑

Answer 7 · 2019-06-04T08:54:07.000Z

brew install watchman worked for me too, thanks!

Answer 8 · 2019-06-07T19:21:19.000Z

I was facing this problem with version of node in 11.15.0, then I changed to v10.15.3 and its gone.

Answer 9 · 2019-06-22T10:30:22.000Z

I'm using jest with react native, every things goes well before I restarted my machine, then I got the same error. Installing watchman didn't solve my problem, I stoped Metro Bundler I deleted build folder from android project I relaunchced my app and it works again.

Answer 10 · 2019-08-07T19:21:51.000Z

brew install watchman worked for me as well. Thanks.

Answer 11 · 2019-08-13T15:03:56.000Z

npm install -g fsevents worked for me.

Answer 12 · 2019-08-18T16:45:37.000Z

npm install fsevents fixed my issue as well. This is on a fresh install of mac osx

Answer 13 · 2019-09-05T18:49:04.000Z

npm install -g fsevents did not work for me
npm install fsevents worked for me, optionally with -D flag

Answer 14 · 2019-09-18T15:33:15.000Z

brew install watchman worked!!! Thanks.

Answer 15 · 2019-09-26T13:41:04.000Z

Nothing helped until...

brew reinstall watchman fixed the problem on node v12.10.0

Answer 16 · 2019-09-28T10:13:12.000Z

brew reinstall watchman works for macOS Mojave, node v12.10.0

Answer 17 · 2019-10-31T02:21:10.000Z

brew install watchman didn't work for me.

npm install --save-dev fsevents worked for me
macOs: Mojave,
node: 12.6.0

Answer 18 · 2019-11-11T15:38:47.000Z

brew install watchman it might work if there's no instance of watchman. In my situation, I had to
brew upgrade watchman and it worked like a charm.

macOs: Catalina
node: 12.12.0

Answer 19 · 2019-11-15T07:28:45.000Z

But why? Anyone can explain why we have to run brew install watchman?

Answer 20 · 2020-01-17T11:08:30.000Z

nvm use then yarn:test worked for me. Turns out it was the wrong version of node.

Answer 21 · 2020-02-15T20:57:23.000Z

brew upgrade watchman worked for me as I already had it installed.

Answer 22 · 2020-02-19T01:30:44.000Z

brew install watchman worked for me.

Answer 23 · 2020-02-19T02:20:42.000Z

You guys should look for the reasons, not just brew install watchman.

There is no documentation says we need install watchman. So why?

Answer 24 · 2020-03-08T04:44:25.000Z

For me I tried all of the above but nothing worked. I had to set the correct nap version. for me I used the following command as I use nvm and have several version of nom installed.

nvm alias default 10.6.0

Hope this will help someone out there.

Answer 25 · 2020-04-28T03:43:29.000Z

@LitoMore The reason being:
https://github.com/facebook/jest/blob/ac267b16e46527d16945fe468f436e46c694fe73/packages/jest-haste-map/src/index.ts#L801

Jest Haste Map has a dependencies on SaneWatcher which can use FB Watchman over fs

// WatchmanWatcher > FSEventsWatcher > sane.NodeWatcher

Answer 26 · 2020-04-28T09:05:34.000Z

@6220119 Thank you so much my Grabber! 🤝

Answer 27 · 2020-05-16T18:22:23.000Z

brew install watchman didn't work for me.

npm install --save-dev fsevents worked for me
macOs: Mojave,
node: 12.6.0

npm install --save-dev fsevents solved the problem. Thanks!

Answer 28 · 2020-06-30T08:29:57.000Z

Run yarn install again worked for me.

Answer 29 · 2020-07-07T02:14:21.000Z

brew upgrade watchman worked for me. I already had watchman installed, but upgraded from node 8 to node 10 and encountered this error.

Answer 30 · 2020-07-16T10:42:15.000Z

In my case all I needed was npm install :)

Answer 31 · 2020-07-22T16:16:40.000Z

brew reinstall watchman works for me too on macOS Catalina, node v12.8.1

Answer 32 · 2020-07-28T13:54:53.000Z

brew upgrade watchman worked for me no node v13.13.0, as I already had it installed.

Answer 33 · 2020-08-05T05:14:00.000Z

the fsevents and node-gyp packages have caused me issues for years, and it seems like nobody understands what actually causes this. i'm on mac os 10.15 but since mac os ~10.12 in like 2017 it's thrown random errors and occasionally messed up npm installs just enough so that i have learned to try random crap until it sort of works without actually figuring it out.

here's some things which have seemed to be related:

messed up python 2 or pip install -- sometimes this is helped by installing python 3.7 or 3.8 and aliasing python to python 3
npm install -g node-gyp or npm install -g fsevents
using npm instead of yarn or vice versa; deleting node_modules and reinstalling; deleting package-lock or yarn.lock and using the other one; etc.
installing or reinstalling xcode command line tools, so that random .h files (frei0r.h is one of three which come up sometimes) which are in /usr/local/include get included by the clang++ compiler

i've shown these issues to people much smarter than me and nobody seems to be able to diagnose the problem. the fact that it sprawls between node, python and even c++ makes me think i'm just not going to figure this out and should just reinstall (although i haven't actually had to yet).

i still have no clue what the central issue is, and whenever i google for related issues i just see threads like this with dozens of people saying "well i tried this and it worked i guess," and eventually, replies like "that didnt work for me." and many of them still get replies, like this one -- the last reply was just 8 days ago.

if the above suggestions don't work, reader, i wish i could help you.

edit: i've seen "try installing or reinstalling watchman" many times and although it clearly works for a lot of people, it's one of the few suggestions that has never improved things for me.

edit 2: i switched to ubuntu because i like laptops with usb and hdmi ports. got a thinkpad and it installed in 15 minutes and i've actually had zero problems, never going back.

Answer 34 · 2020-10-17T06:55:28.000Z

brew install watchman, this works!!

Answer 35 · 2020-12-17T16:23:57.000Z

brew install watchman fixed the problem for me.

cm-pliser-tdd-by-example/tdd-by-example-js#10 (comment)

This worked for me!! brew install watchman, then when running the test suite again I needed to grant some permissions to watchman.

Answer 36 · 2021-01-20T11:47:30.000Z

brew install watchman worked for me also.

However, i stumbled across a non-related issue to do with excessive node process CPU usage when idle (~250%), and so i downloaded and re-installed Command Line Tools for Xcode, and then restarted my machine (that's important), which appears to resolve the excessive node CPU usage issue, and by coincidence it looks to have also resolved the Jest Watch mode issue too, without the need for the brew dependency; watchman after i carried out a Jest Watch mode test run after uninstalling the dependency; brew uninstall watchman.

Not sure specifically why this approach to reinstalling Command Line Tools for Xcode works to resolve the Jest Watch mode issue as described on this ticket, which i had also suffered from.

But this may provide an alternative approach for others who may like to avoid installing additional dependencies such as watchman, where possible, to workaround the Jest Watch mode issue.

Answer 37 · 2021-03-18T12:35:50.000Z

I was using Node 15 but the project was created in the Node 8 days. Fix for me was:

- nvm install 8
- rm -rf node_modules/
- npm install

This is why all projects should have an .nvmrc.

Answer 38 · 2021-08-08T21:08:46.000Z

brew install watchman didn't work for me.

npm install --save-dev fsevents worked for me

macos: Big Sur
Node version : 12

Answer 39 · 2021-10-08T07:50:26.000Z

使用这个命令安装就好了 npm install --save-dev fsevents