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

npm start fails, gives start script error #34

Open
Tamenze opened this issue Aug 13, 2017 · 2 comments
Open

npm start fails, gives start script error #34

Tamenze opened this issue Aug 13, 2017 · 2 comments

Comments

@Tamenze
Copy link

Tamenze commented Aug 13, 2017

i'm at the very beginning of this project. after installing npm packages and typing npm start, i get the following in the console:

> concurrently "npm run server" "npm run client"

[0] 
[0] > [email protected] server /Users/tamenze/Desktop/newDuck/food-lookup-demo
[0] > node server.js
[0] 
[1] 
[1] > [email protected] client /Users/tamenze/Desktop/newDuck/food-lookup-demo
[1] > node start-client.js
[1] 
[1] 
[1] > [email protected] start /Users/tamenze/Desktop/newDuck/food-lookup-demo/client
[1] > react-scripts start
[1] 
[0] Find the server at: http://localhost:3000/
[1] Something is already running on port 3000.

And the view shows a "Cannot GET /" I've checked and nothing else is running on that port, and I've even used lsof -i tcp:3000, to no avail.
And When I exit npm, I get the following error:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `concurrently "npm run server" "npm run client"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

@fleawig
Copy link

fleawig commented Aug 9, 2018

I'm having the exact same problem with the exact same error messages. Did you ever make any progress with this?

The server seems to work--it responds to http requests--but the client isn't connecting to it.
The only clue I've stumbled upon so far is that git mentions uncommitted changes to the package-lock.json when I try to checkout starting-point.

@bendozy
Copy link

bendozy commented Aug 22, 2018

Did you run npm install in the client directory? That was the step I missed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants