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 failed when running react-react-app #1502

Closed
jordyvandomselaar opened this issue Feb 8, 2017 · 4 comments
Closed

react-scripts failed when running react-react-app #1502

jordyvandomselaar opened this issue Feb 8, 2017 · 4 comments

Comments

@jordyvandomselaar
Copy link

Description

A bug

Expected behavior

A working read app gets generated

Actual behavior

package.json does not contain any scripts; nom start doesn't work.

Stack trace when creating a new app:


Installing packages. This might take a couple minutes.
Installing react-scripts...

npm install --save-dev --save-exact react-scripts failedallel extract 820```
### Environment

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

1. `npm ls react-scripts` (if you haven’t ejected): 
```npm ls react-scriptseggheads-radio@0.1.0 /home/vagrant/projects/eggheads-radio
└── (empty)
  1. node -v: v7.5.0
  2. npm -v: 4.1.2

Then, specify:

  1. Operating system: Ubuntu trusty tahr
  2. Browser and version: Not applicable.
@gaearon
Copy link
Contributor

gaearon commented Feb 8, 2017

As you can see, running npm install failed:

npm install --save-dev --save-exact react-scripts failedallel extract 820```

(I presume there's more in the log but your report cut it off.)

We need to provide better error handling, but basically this means npm install failed on your machine for some reason. This could be a network issue, or some local problem with npm.

Can you try again? If it fails, can you post the complete npm output?
Thanks!

@gaearon
Copy link
Contributor

gaearon commented Feb 9, 2017

Going to close this since it's an npm issue (and likely due to the network), but filed #1505 so that we handle this more gracefully in the future.

@gaearon gaearon closed this as completed Feb 9, 2017
@kabakovda
Copy link

you can get this error if you have low memory.

@astannard
Copy link

I had this issue and spent a long while trying to fix it, this is what worked for me. uninstalling and then reinstalling yarn. Then all worked fine, hope that helps someone

@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

4 participants