start: react-scripts start
[2] npm ERR! spawn ENOENT
[2] npm ERR!
[2] npm ERR! Failed at the phpokedex@0.1.0 start script.
[2] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[2] npm WARN Local package.json exists, but node_modules missing, did you mean to install?
[2]
[2] npm ERR! A complete log of this run can be found in:
[2] npm ERR! /Users/medium/.npm/_logs/2023-07-03T16_58_23_443Z-debug.log
[2] npm ERR! code ELIFECYCLE
[2] npm ERR! errno 1
[2] npm ERR! fill_cont@1.0.0 client: npm start --prefix client
[2] npm ERR! Exit status 1
[2] npm ERR!
[2] npm ERR! Failed at the fill_cont@1.0.0 client script.
[2] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[2]
[2] npm ERR! A complete log of this run can be found in:
[2] npm ERR! /Users/medium/.npm/_logs/2023-07-03T16_58_23_905Z-debug.log
[2] npm run client exited with code 1
[1] Drink up on Port: 5000
"scripts": {
"start": "webpack serve --mode development",
"build": "webpack --mode production && mv build ../",
"server": "nodemon --quiet server",
"client": "npm start --prefix client",
"dev": "concurrently \"npm run start\" \"npm run server\" \"npm run client\""
},
heeding a random reddit comment that: it'll be faster to change to parcel or vite.js than it will be to fix webpack.
I believe this opinion to be truthy.
later in the logs webpack is mentioned again:
[0] [webpack-dev-server] Content not from webpack is served from '/Users/medium/Desktop/fill_cont/public' directory
[0] asset bundle.js 9.22 MiB [emitted] (name: main)
start:
react-scripts start[2] npm ERR! spawn ENOENT [2] npm ERR! [2] npm ERR! Failed at the phpokedex@0.1.0 start script. [2] npm ERR! This is probably not a problem with npm. There is likely additional logging output above. [2] npm WARN Local package.json exists, but node_modules missing, did you mean to install? [2] [2] npm ERR! A complete log of this run can be found in: [2] npm ERR! /Users/medium/.npm/_logs/2023-07-03T16_58_23_443Z-debug.log [2] npm ERR! code ELIFECYCLE [2] npm ERR! errno 1 [2] npm ERR! fill_cont@1.0.0 client:npm start --prefix client[2] npm ERR! Exit status 1 [2] npm ERR! [2] npm ERR! Failed at the fill_cont@1.0.0 client script. [2] npm ERR! This is probably not a problem with npm. There is likely additional logging output above. [2] [2] npm ERR! A complete log of this run can be found in: [2] npm ERR! /Users/medium/.npm/_logs/2023-07-03T16_58_23_905Z-debug.log [2] npm run client exited with code 1 [1] Drink up on Port: 5000"scripts": { "start": "webpack serve --mode development", "build": "webpack --mode production && mv build ../", "server": "nodemon --quiet server", "client": "npm start --prefix client", "dev": "concurrently \"npm run start\" \"npm run server\" \"npm run client\"" },
heeding a random reddit comment that: it'll be faster to change to parcel or vite.js than it will be to fix webpack. I believe this opinion to be truthy.
later in the logs webpack is mentioned again:
[0] [webpack-dev-server] Content not from webpack is served from '/Users/medium/Desktop/fill_cont/public' directory [0] asset bundle.js 9.22 MiB [emitted] (name: main)
[1:05pm]