'react-scripts' is not recognized as an internal or external command, operable program or batch file.

[marko-mlinarevic]

Note from maintainers: if you came here from search, your issue is likely unrelated to this thread. Just run npm install before npm start and you’ll be fine. See the explanation.

---

Description

I followed instructions when setting up sass but after did the last step I get error in the title

these are scripts in json package

"scripts": {
"build-css": "node-sass src/ -o src/",
"watch-css": "npm run build-css && node-sass src/ -o src/ --watch --recursive",
"start-js": "react-scripts start",
"start": "npm-run-all -p watch-css start-js",
"build": "npm run build-css && react-scripts build",
"test": "react-scripts test --env=jsdom",
"eject": "react-scripts eject"
},

Expected behavior

If it was normal it would start the server and it would compile sass files

Actual behavior

In cli it should run script normally but I get error 'react-scripts' is not recognized as an internal or external command, operable program or batch file.'

'react-scripts' is not recognized as an internal or external command, operable program or batch file.

Environment

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

1. npm ls react-scripts (if you haven’t ejected): `--(empty)
2. node -v: v7.0.0
3. npm -v: v3.10.8

Then, specify:

1. Operating system: Windows_NT 10.0.14393

[gaearon]

Does this variation work?

"scripts": {
  "build-css": "node-sass src/ -o src/",
  "build-js": "react-scripts build",
  "build": "npm run build-css && npm run build-js",
  "start-css": "npm run build-css && npm run build-css -- --watch --recursive",
  "start-js": "react-scripts start",
  "start": "npm-run-all -p start-css start-js",
  "test": "react-scripts test --env=jsdom",
  "eject": "react-scripts eject"
},

[gaearon]

(Update: edited suggestion above. Can you try the last version I posted?)

[marko-mlinarevic]

It doesn't work. I forgot to add this part of error

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\User\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v7.0.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! WeatherApp@0.1.0 start: `npm-run-all -p start-css start-js`
npm ERR! Exit status 1

[gaearon]

Could it be that your node_modules is corrupted?
Can you run npm install and try again?

If it doesn't work please post the complete output again.

[marko-mlinarevic]

I tried it.... same error. This is entire output

'react-scripts' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\OunknownO\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "start-js"
npm ERR! node v7.0.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! WeatherApp@0.1.0 start-js: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the WeatherApp@0.1.0 start-js script 'react-scripts start'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the WeatherApp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     react-scripts start
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs WeatherApp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls WeatherApp
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\OunknownO\AppData\Roaming\npm-cache\_logs\2017-02-24T09_33_23_854Z-debug.log
ERROR: "start-js" exited with 1.

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\OunknownO\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v7.0.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! WeatherApp@0.1.0 start: `npm-run-all -p start-css start-js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the WeatherApp@0.1.0 start script 'npm-run-all -p start-css start-js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the WeatherApp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm-run-all -p start-css start-js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs WeatherApp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls WeatherApp
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\OunknownO\AppData\Roaming\npm-cache\_logs\2017-02-24T09_33_24_779Z-debug.log

E:\PrivatniProjekti\WeatherApp>
> WeatherApp@0.1.0 build-css E:\PrivatniProjekti\WeatherApp
> node-sass src/ -o src/

No input file was found.

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\OunknownO\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "build-css"
npm ERR! node v7.0.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! WeatherApp@0.1.0 build-css: `node-sass src/ -o src/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the WeatherApp@0.1.0 build-css script 'node-sass src/ -o src/'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the WeatherApp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-sass src/ -o src/
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs WeatherApp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls WeatherApp
npm ERR! There is likely additional logging output above.

[gaearon]

@mysticatea Do you think you could shed any light on this? npm-run-all works fine with the same commands on macOS, do you know if there are any issues on Windows?

[gaearon]

Wait...

You're saying npm ls react-scripts gives you no results? This definitely means your installation is botched somehow.

Can you show your full package.json and a screenshot of react-scripts in your node_modules folder?

[gaearon]

Did you do anything to your project folder at all? Like, move it somewhere, or copy and paste files.

[marko-mlinarevic]

nop, i didn't move it but I don't see react-scripts folder in node_modules.

[gaearon]

Can you show me the full package.json?

[marko-mlinarevic]

{
  "name": "WeatherApp",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "autoprefixer": "6.5.1",
    "babel-core": "6.17.0",
    "babel-eslint": "7.1.1",
    "babel-jest": "17.0.2",
    "babel-loader": "6.2.7",
    "babel-preset-react-app": "^2.0.1",
    "case-sensitive-paths-webpack-plugin": "1.1.4",
    "chalk": "1.1.3",
    "connect-history-api-fallback": "1.3.0",
    "cross-spawn": "4.0.2",
    "css-loader": "0.26.0",
    "detect-port": "1.0.1",
    "dotenv": "2.0.0",
    "eslint": "3.8.1",
    "eslint-config-react-app": "^0.5.0",
    "eslint-loader": "1.6.0",
    "eslint-plugin-flowtype": "2.21.0",
    "eslint-plugin-import": "2.0.1",
    "eslint-plugin-jsx-a11y": "2.2.3",
    "eslint-plugin-react": "6.4.1",
    "extract-text-webpack-plugin": "1.0.1",
    "file-loader": "0.9.0",
    "filesize": "3.3.0",
    "fs-extra": "0.30.0",
    "gzip-size": "3.0.0",
    "html-webpack-plugin": "2.24.0",
    "http-proxy-middleware": "0.17.2",
    "jest": "17.0.2",
    "json-loader": "0.5.4",
    "node-sass": "^4.5.0",
    "npm-run-all": "^4.0.2",
    "object-assign": "4.1.0",
    "path-exists": "2.1.0",
    "postcss-loader": "1.0.0",
    "promise": "7.1.1",
    "react-dev-utils": "^0.4.2",
    "recursive-readdir": "2.1.0",
    "strip-ansi": "3.0.1",
    "style-loader": "0.13.1",
    "url-loader": "0.5.7",
    "webpack": "1.14.0",
    "webpack-dev-server": "1.16.2",
    "webpack-manifest-plugin": "1.1.0",
    "whatwg-fetch": "1.0.0"
  },
  "dependencies": {
    "react": "^15.4.2",
    "react-dom": "^15.4.2",
    "react-redux": "^5.0.2",
    "redux": "^3.6.0",
    "redux-logger": "^2.8.1",
    "redux-promise-middleware": "^4.2.0",
    "redux-thunk": "^2.2.0"
  },
  "scripts": {
    "build-css": "node-sass src/ -o src/",
    "watch-css": "npm run build-css && node-sass src/ -o src/ --watch --recursive",
    "start-js": "react-scripts start",
    "start": "npm-run-all -p watch-css start-js",
    "build": "npm run build-css && react-scripts build",
    "test": "react-scripts test --env=jsdom",
    "eject": "react-scripts eject"
  },
  "jest": {
    "collectCoverageFrom": [
      "src/**/*.{js,jsx}"
    ],
    "setupFiles": [
      "<rootDir>\\config\\polyfills.js"
    ],
    "testPathIgnorePatterns": [
      "<rootDir>[/\\\\](build|docs|node_modules)[/\\\\]"
    ],
    "testEnvironment": "node",
    "testURL": "http://localhost",
    "transform": {
      "^.+\\.(js|jsx)$": "<rootDir>/node_modules/babel-jest",
      "^.+\\.css$": "<rootDir>\\config\\jest\\cssTransform.js",
      "^(?!.*\\.(js|jsx|css|json)$)": "<rootDir>\\config\\jest\\fileTransform.js"
    },
    "transformIgnorePatterns": [
      "[/\\\\]node_modules[/\\\\].+\\.(js|jsx)$"
    ],
    "moduleNameMapper": {
      "^react-native$": "react-native-web"
    }
  },
  "babel": {
    "presets": [
      "react-app"
    ]
  },
  "eslintConfig": {
    "extends": "react-app"
  }
}

[marko-mlinarevic]

I apologize for wasting your time, it seems that my colleague did "eject"

[gaearon]

You didn't mention that you ejected. 😉

[gaearon]

Right. So you'll need to replace react-scripts <something> from the docs with node scripts/<something>.js to match what your start and build scripts currently say.