Error in jest watch when using yarn for dependency installation #1474

aztecrex · 2017-01-31T03:07:54Z

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.

Can you reproduce the problem with latest npm?

Can you still reproduce it?

Yes.

Description

npm test, yarnpkg test, yarn test all fail when dependencies are installed with
yarn install. They all work fine when dependencies are installed with npm install.

In CI mode (not watched), tests run fine after installing deps with yarn. Research indicates others are having similar problems with tools like Watchman which leads me to believe that something is different in how Jest is performing the watch depending on how it is installed. There is also a
sense that this has to do with OSX Sierra.

Expected behavior

Tests run

Actual behavior

Crash. See stack trace beow.

Environment

Run these commands in the project folder and fill in their results:

npm ls react-scripts: react-scripts@0.8.5
node -v: v7.4.0
npm -v: 4.1.2

Then, specify:

Operating system: Darwin trefoil 16.3.0 Darwin Kernel Version 16.3.0: Thu Nov 17 20:23:58 PST 2016; root:xnu-3789.31.2~1/RELEASE_X86_64 x86_64
Browser and version: Not a browser isssue

Reproducible Demo

Easy: this happens from a fresh create-react-app when Yarn (freshly brewed today)
is installed. yarnpkg test will fail. Now delete node_modules and run
npm install now npm test works fine. delete node_modues and run
yarn install, bad behavior returns.

Push to GitHub and paste the link here.

https://github.com/aztecrex/demo-create-react-app-yarn-problem

Full stack trace:

2017-01-30 18:58 node[77220] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-01-30 18:58 node[77220] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-01-30 18:58 node[77220] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-01-30 18:58 node[77220] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-01-30 18:58 node[77220] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-01-30 18:58 node[77220] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-01-30 18:58 node[77220] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-01-30 18:58 node[77220] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-01-30 18:58 node[77220] (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:1022:11)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1283:11)
error Command failed with exit code 1.

The text was updated successfully, but these errors were encountered:

gaearon · 2017-01-31T14:52:12Z

Can you check if node_modules/fsevents exists after installing with either Yarn or npm?

robertlyall · 2017-01-31T16:50:43Z

I'm having the same problem with version 1.0.3.

fsevents existed in my node_modules directory after installing with npm install, yarn install and yarnpkg install, however I could only run tests after installing with npm.

gaearon · 2017-01-31T17:03:03Z

Which version of Yarn are you using?

robertlyall · 2017-01-31T17:04:35Z

I'm using Yarn version 0.19.1.

gaearon · 2017-01-31T17:04:53Z

Could this be a regression? Would you mind installing 0.18 and trying again?

robertlyall · 2017-01-31T17:15:53Z

Experiencing the same problem with 0.18.0, 0.18.1 and 0.20.0.

It may be worth noting that I'm using Yarn installed globally via NPM. I can try again using Homebrew if you'd like?

aztecrex · 2017-01-31T17:25:31Z

The one giving me trouble is 0.19.1 installed via Homebrew. That was my first version so can't brew switch

gaearon · 2017-01-31T17:40:59Z

Can you figure out what the difference between installs produced by Yarn and npm is? Is some package or binary missing?

robertlyall · 2017-01-31T18:11:41Z

I'm not sure what's the best way to do that. Do you have any suggestions?

I ran npm ls after yarn install and saw the following error:

npm ERR! extraneous: node-pre-gyp@0.6.32 /path/to/project/node_modules/node-pre-gyp

npm start does not show the same error. I don't know whether this error is important or not.

hongrich · 2017-01-31T18:22:39Z

Is this the same as #871? Maybe try installing watchman?

aztecrex · 2017-01-31T18:22:50Z

i just pushed the repo with both node_modules and a diff, https://github.com/aztecrex/demo-create-react-app-yarn-problem. Interesting, here is the result of du -sh *

 60K	README.md
 11M	node_modules.diff
127M	node_modules.npm
531M	node_modules.yarn
4.0K	package.json
 32K	public
 24K	src

(node_modules_diff is just the text output of diff -r node_modules.*)

aztecrex · 2017-01-31T18:32:18Z

@hongrich i had tried that yesterday. I just tried it again: install watchman, delete node_modules, yarn install. I get many warnings before jest gives me the watch UI, for example:

jest-haste-map: duplicate manual mock found:
  Module name: fetchWithRetries
  Duplicate Mock path: /Users/aztecrex/Working/demo-create-react-app-yarn-problem/node_modules.npm/fbjs/lib/__mocks__/fetchWithRetries.js
This warning is caused by two manual mock files with the same file name.
Jest will use the mock file found in:
/Users/aztecrex/Working/demo-create-react-app-yarn-problem/node_modules.npm/fbjs/lib/__mocks__/fetchWithRetries.js
 Please delete one of the following two files:
 /Users/aztecrex/Working/demo-create-react-app-yarn-problem/node_modules.yarn/fbjs/lib/__mocks__/fetchWithRetries.js
/Users/aztecrex/Working/demo-create-react-app-yarn-problem/node_modules.npm/fbjs/lib/__mocks__/fetchWithRetries.js

When i press a, It runs and fails a bunch of tests I don't have (this is just a newly-created CRA so it should have just one), for example,

  ● main export › should export propName from root

    ENOENT: no such file or directory, stat '/Users/aztecrex/Working/demo-create-react-app-yarn-problem/propName.js'

      at Object.fs.statSync (fs.js:907:18)
      at Object.it (node_modules.npm/jsx-ast-utils/__tests__/src/index-test.js:

After I uninstall watchman, the behavior goes back to the one described in this report.

gaearon · 2017-01-31T19:49:37Z

I get many warnings before jest gives me the watch UI, for example

This is because of those node_modules.npm and node_modules.yarn folders which conflict. I wonder if there’s a way to disable Haste completely in open source with some config option, cc @cpojer? It’s not really useful to CRA users.

aztecrex · 2017-01-31T21:33:23Z

Removed those dirs and the "install watchman" workaround fixes the problem. Uninstalling watchman causes it to re-occur.

@hongrich glad I tried it again

cpojer · 2017-02-01T13:50:42Z

@gaearon yeah we are making some changes that should improve this situation.

gaearon · 2017-02-11T20:12:24Z

Going to close since this is out of our control.
If you have issues with Yarn please report them, and use npm while they are being fixed.

tsironis · 2017-02-20T16:12:21Z

I fixed the issue upgrading yarn to v0.20.1 and then brew install watchman. Apparently, there is a problem watching file changes in macOS Sierra.

gaearon · 2017-02-20T17:44:14Z

Apparently, there is a problem watching file changes in macOS Sierra.

If your tests hang, that's not the problem described in this issue. For that problem, please see here.

tsironis · 2017-02-24T15:25:24Z

Sorry my bad! I didn't describe this correctly, I meant FSWatcher is not longer available in macOS Sierra so watchman is required.

bholtbholt · 2018-03-24T22:20:08Z

I hit this issue today on macOS High Sierra using Yarn. Deleting my node_modules and rerunning yarn fixed it for me.

gaearon mentioned this issue Jan 31, 2017

Yarn + Create React App Umbrella #1189

Closed

12 tasks

gaearon closed this as completed Jan 31, 2017

gaearon reopened this Jan 31, 2017

gaearon added issue: bug tag: underlying tools labels Jan 31, 2017

gaearon closed this as completed Feb 11, 2017

just-boris mentioned this issue Apr 5, 2017

Add note about installing watchman #1933

Closed

lock bot locked and limited conversation to collaborators Jan 20, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error in jest watch when using yarn for dependency installation #1474

Error in jest watch when using yarn for dependency installation #1474

aztecrex commented Jan 31, 2017 •

edited

Loading

gaearon commented Jan 31, 2017

robertlyall commented Jan 31, 2017

gaearon commented Jan 31, 2017

robertlyall commented Jan 31, 2017

gaearon commented Jan 31, 2017

robertlyall commented Jan 31, 2017 •

edited

Loading

aztecrex commented Jan 31, 2017 •

edited

Loading

gaearon commented Jan 31, 2017

robertlyall commented Jan 31, 2017 •

edited

Loading

hongrich commented Jan 31, 2017

aztecrex commented Jan 31, 2017 •

edited

Loading

aztecrex commented Jan 31, 2017 •

edited

Loading

gaearon commented Jan 31, 2017

aztecrex commented Jan 31, 2017

cpojer commented Feb 1, 2017

gaearon commented Feb 11, 2017

tsironis commented Feb 20, 2017

gaearon commented Feb 20, 2017

tsironis commented Feb 24, 2017

bholtbholt commented Mar 24, 2018

Error in jest watch when using yarn for dependency installation #1474

Error in jest watch when using yarn for dependency installation #1474

Comments

aztecrex commented Jan 31, 2017 • edited Loading

Can you reproduce the problem with latest npm?

Description

Expected behavior

Actual behavior

Environment

Reproducible Demo

gaearon commented Jan 31, 2017

robertlyall commented Jan 31, 2017

gaearon commented Jan 31, 2017

robertlyall commented Jan 31, 2017

gaearon commented Jan 31, 2017

robertlyall commented Jan 31, 2017 • edited Loading

aztecrex commented Jan 31, 2017 • edited Loading

gaearon commented Jan 31, 2017

robertlyall commented Jan 31, 2017 • edited Loading

hongrich commented Jan 31, 2017

aztecrex commented Jan 31, 2017 • edited Loading

aztecrex commented Jan 31, 2017 • edited Loading

gaearon commented Jan 31, 2017

aztecrex commented Jan 31, 2017

cpojer commented Feb 1, 2017

gaearon commented Feb 11, 2017

tsironis commented Feb 20, 2017

gaearon commented Feb 20, 2017

tsironis commented Feb 24, 2017

bholtbholt commented Mar 24, 2018

aztecrex commented Jan 31, 2017 •

edited

Loading

robertlyall commented Jan 31, 2017 •

edited

Loading

aztecrex commented Jan 31, 2017 •

edited

Loading

robertlyall commented Jan 31, 2017 •

edited

Loading

aztecrex commented Jan 31, 2017 •

edited

Loading

aztecrex commented Jan 31, 2017 •

edited

Loading