You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
npm install throwing error on GCP Cloud hosted Ubuntu 18.04 LTS
To Reproduce
Steps to reproduce the behavior:
Go to Cloud console
cd to expense-manager-react
enter command npm start
See error
Screenshots
Desktop (please complete the following information):
OS: Ubuntu 18.04
Error Details
root@money-mgmt:/opt/expense-manager-react# npm start
> [email protected] start /opt/expense-manager-react
> react-scripts start
sh: 1: react-scripts: not found
npm ERR! Linux 4.15.0-1037-gcp
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] start: `react-scripts start`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] start 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 expense-manager-react 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 expense-manager-react
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls expense-manager-react
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /opt/expense-manager-react/npm-debug.log
The text was updated successfully, but these errors were encountered:
Describe the bug
npm install throwing error on GCP Cloud hosted Ubuntu 18.04 LTS
To Reproduce
Steps to reproduce the behavior:
npm start
Screenshots
Desktop (please complete the following information):
Error Details
The text was updated successfully, but these errors were encountered: