npm start not working with react bulma components included

Question

When I try to launch my react app using npm start, it doesn't work and gives me the following response.

Michaels-MBP:compare-react michaelwroquemore$ npm start

[email protected] start npm-run-all -p watch-css start-js

[email protected] start-js react-scripts start

[email protected] watch-css npm run build-css && node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/ --watch --recursive

[email protected] build-css node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/

sh: node-sass-chokidar: command not found ERROR: "watch-css" exited with 127. Michaels-MBP:compare-react michaelwroquemore$

---

The react app server was live and working before. Then, I attempted to integrate bulma react components as specified on the page in the following link. https://medium.com/frontendweb/install-react-bulma-components-in-my-react-app-3f127afd77e7

I ran npm install react-bulma-components

I included the following on my index.js file: import 'react-bulma-components/dist/react-bulma-components.min.css';

I ran npm install node-sass --save-dev

Then I ran npm install bulma.

FINALLY (while still inside the react app folder), I ran npm install node-sass-chokidar and npm install --save-dev npm-run-all.

After all of this, when I run "npm start" in the terminal, I get the same response that I mentioned above.

Here is my "scripts" package.

"scripts": {
  "build-css": "node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/",
  "watch-css": "npm run build-css && node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/ --watch --recursive",
  "start-js": "react-scripts start",
  "start": "npm-run-all -p watch-css start-js",
  "build-js": "react-scripts build",
  "build": "npm-run-all build-css build-js",
  "test": "react-scripts test",
  "eject": "react-scripts eject"
},

I THOUGHT that I already added all of the necessary changes to the scripts, but perhaps there is some problem there.

As a final note on trouble shooting, I have already tried running:

npm update chokidar

and

npm update --force

Any ideas on what I can try?