npm start doesn't works

描述

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

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

貢獻者指南

技術棧

reactjavascriptnodejs

領域

documentationdeveloper experience

議題類型

bug

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

2

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

under 1 hour

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

stale

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

clear

前置要求

npmcommand line basics

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

85

研究方向

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.