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

Upgrade Node to 7.7.2 prevents react-scripts from running #1782

Closed
caseybaggz opened this issue Mar 9, 2017 · 3 comments
Closed

Upgrade Node to 7.7.2 prevents react-scripts from running #1782

caseybaggz opened this issue Mar 9, 2017 · 3 comments

Comments

@caseybaggz
Copy link

Can you reproduce the problem with latest npm?

yes

Description

When upgraded to Node 7.7.2 then running yarn start, react-scripts errored and prevented running.

This only happens with yarn start. yarn test & build work fine.

Actual behavior

yarn start v0.21.3
$ react-scripts start
(node:23359) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: "listener" argument must be a function
(node:23359) DeprecationWarning: Unhandled promise rejections are deprecated.In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
✨  Done in 0.90s.

Still received error after running:

$ rm -rf node_modules
$ yarn cache clean
$ npm cache clean
$ yarn

Environment

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

  1. npm ls react-scripts (if you haven’t ejected): react-scripts@0.9.4
  2. node -v: v7.7.2
  3. npm -v: 4.1.2

Then, specify:

  1. Operating system: MacOS Seirra 10.12.2
  2. Browser and version: na

Reproducible Demo

Created new app and ran yarnpkg start and still got error:

$ react-scripts start
(node:30965) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: "listener" argument must be a function
(node:30965) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
✨  Done in 1.07s.
@vhain
Copy link

vhain commented Mar 9, 2017

I think it's duplicate of #1776

@gaearon
Copy link
Contributor

gaearon commented Mar 9, 2017

It is.

@gaearon gaearon closed this as completed Mar 9, 2017
@gaearon
Copy link
Contributor

gaearon commented Mar 9, 2017

@lock lock bot locked and limited conversation to collaborators Jan 22, 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