Can't run on Windows 10 #16
Description
It took quite some time to get all the depencies, but I managed to do it, and this is what happens when I try to run the project. (Sorry for the poor formatting) fixed thanks to @SuperSandro2000!
I guess it seems like a Windows issue?
> [email protected] start C:\Users\User\Documents\Whatsapp\Web\whatsapp-web-reveng
> npm run dev
> [email protected] dev C:\Users\User\Documents\Whatsapp\Web\whatsapp-web-reveng
> concurrently --kill-others "./node_modules/.bin/nodemon index.js -i client -e js" "./node_modules/.bin/nodemon --exec python ./backend/whatsapp-web-backend.py -i client -e py" "sass --sourcemap=none --watch client/css/main.scss:client/css/main.css"
[0] '.' is not recognized as an internal or external command,
[0] operable program or batch file.
[1] '.' is not recognized as an internal or external command,
[1] operable program or batch file.
[1] ./node_modules/.bin/nodemon --exec python ./backend/whatsapp-web-backend.py -i client -e py exited with code 1
--> Sending SIGTERM to other processes..
[0] ./node_modules/.bin/nodemon index.js -i client -e js exited with code 1
[2] sass --sourcemap=none --watch client/css/main.scss:client/css/main.css exited with code 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] dev: `concurrently --kill-others "./node_modules/.bin/nodemon index.js -i client -e js" "./node_modules/.bin/nodemon --exec python ./backend/whatsapp-web-backend.py -i client -e py" "sass --sourcemap=none --watch client/css/main.scss:client/css/main.css"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] dev 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! C:\Users\User\AppData\Roaming\npm-cache\_logs\2018-04-10T17_58_26_327Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `npm run dev`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! C:\Users\User\AppData\Roaming\npm-cache\_logs\2018-04-10T17_58_26_501Z-debug.log````