kentcdodds/advanced-react-patterns-v2

npm start doesn't works

Open

#52 opened on Nov 25, 2018

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (1,504 stars) (578 forks)batch import
help wantedneeds investigation

Description

On windows, this project ran fine.

However, on my Mac. Following the same steps gives me an error


sh: react-scripts: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! advanced-react-patterns-v2@1.0.0 start: `react-scripts start`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the advanced-react-patterns-v2@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/vedant/.npm/_logs/2018-11-25T05_46_33_446Z-debug.log

I tried

1. rm -rf node-modules && npm install && npm start
2. npm i -D react-scripts && npm start

And it still fails

Contributor guide

Tech stack
reactjavascriptnodejs
Domain
documentationdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
npmcommand line basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
The issue is that `react scripts start` fails with 'command not found' on macOS. The user already tried removing node modules and reinstalling, and installing react scripts locally, but still fails. This suggests an environment issue possibly related to Node.js version or missing global dependencies. The fix likely involves updating the project's setup documentation to include platform specific instructions, or ensuring that the package.json includes all necessary dependencies. Review the current README and package.json (especially the scripts and dependencies sections) to identify what's missing. Consider adding a .nvmrc file and clarifying that `npm install` must be run before `npm start`. The issue is self contained and requires minimal code changes, making it ideal for a first time contributor.