Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

react-scripts pins fsevents to a version too old for Node 10 #4896

Closed
Jessidhia opened this issue Aug 17, 2018 · 2 comments
Closed

react-scripts pins fsevents to a version too old for Node 10 #4896

Jessidhia opened this issue Aug 17, 2018 · 2 comments

Comments

@Jessidhia
Copy link

Is this a bug report?

Yes

Did you try recovering your dependencies?

Yes. I have also attempted working around it with a yarn resolutions field, but it seems yarn resolutions turn optional dependencies into required dependencies.

Which terms did you search for in User Guide?

fsevents

Environment

Environment:
  OS:  macOS 10.14
  Node:  10.5.0
  Yarn:  1.9.2
  npm:  6.1.0
  Watchman:  Not Found
  Xcode:  Xcode 10.0 Build version 10L201y
  Android Studio:  Not Found

Packages: (wanted => installed)
  react: ^16.3.1 => 16.4.1
  react-dom: ^16.3.1 => 16.4.1
  react-scripts: 2.0.0-next.3e165448 => 2.0.0-next.3e165448

Steps to Reproduce

(Write your steps here:)

  1. Use node >= 10.4.1 on macOS
  2. Create a new project with create-react-app
  3. fsevents fails to build fsevents/fsevents#226 happens during yarn install

Expected Behavior

No build errors

Actual Behavior

Huge build error that is elaborated upon on
fsevents/fsevents#226


Updating fsevents to 1.2.4, or to a caret version (^1.2.4) is sufficient to avoid the build error.

@Timer
Copy link
Contributor

Timer commented Sep 21, 2018

Updated on next.

@Timer Timer closed this as completed Sep 21, 2018
@Timer Timer reopened this Sep 21, 2018
@Timer Timer closed this as completed Sep 21, 2018
@iabotsiTC
Copy link

Had the same problem here, resolved by removing yarn.lock and re-run yarn install. Hope it can help...

@lock lock bot locked and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants