Я изменил настройку, потому что у меня были всевозможные ошибки при попытке установить styled-компоненты. Я установил это, но теперь, когда я пытаюсь запустить NPM Start, я получаю больше ошибок. Я даже пытался удалить и переустановить NODE.JS ...
После того, как я попытался запустить NPM Запуск в каталоге моего проекта, я получаю это сообщение об ошибке:
npm ERR! syscall spawn C:\Program Files\Git\bin\bash.exe
npm ERR! file C:\Program Files\Git\bin\bash.exe
npm ERR! path C:\Program Files\Git\bin\bash.exe
npm ERR! errno ENOENT
npm ERR! dicegame@0.1.0 start: `react-scripts start`
npm ERR! spawn C:\Program Files\Git\bin\bash.exe ENOENT
npm ERR!
npm ERR! Failed at the dicegame@0.1.0 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\rickb\AppData\Roaming\npm-cache\_logs\2020-04-30T16_18_42_683Z-debug.log
и вот debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm@6.14.4
3 info using node@v12.16.2
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle dicegame@0.1.0~prestart: dicegame@0.1.0
6 info lifecycle dicegame@0.1.0~start: dicegame@0.1.0
7 verbose lifecycle dicegame@0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle dicegame@0.1.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\rickb\Desktop\Coding\portfolio\diceGame\dicegame\node_modules\.bin;C:\Program Files\AdoptOpenJDK\jre-8.0.252.09-hotspot\bin;C:\Program Files (x86)\AdoptOpenJDK\jre-8.0.252.09-hotspot\bin;C:\Python38\Scripts\;C:\Python38\;C:\Program Files\AdoptOpenJDK\jdk-11.0.6.10-hotspot\bin;C:\Program Files\Amazon Corretto\jdk11.0.6_10\bin;C:\Program Files\Amazon Corretto\jdk1.8.0_242\bin;C:\Program Files (x86)\Amazon Corretto\jdk1.8.0_242\bin;C:\Program Files\AdoptOpenJDK\jdk-8.0.242.08-hotspot\bin;C:\Program Files (x86)\AdoptOpenJDK\jdk-8.0.242.08-hotspot\bin;C:\Program Files\AdoptOpenJDK\jre-11.0.6.10-hotspot\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft VS Code\bin;C:\ProgramData\chocolatey\bin;C:\Program Files (x86)\Yarn\bin\;C:\Program Files\nodejs\;C:\Users\rickb\AppData\Local\Microsoft\WindowsApps;C:\Users\rickb\AppData\Local\GitHubDesktop\bin;C:\Users\rickb\AppData\Local\Yarn\bin;C:\Users\rickb\AppData\Roaming\npm
9 verbose lifecycle dicegame@0.1.0~start: CWD: C:\Users\rickb\Desktop\Coding\portfolio\diceGame\dicegame
10 silly lifecycle dicegame@0.1.0~start: Args: [ '-c', 'react-scripts start' ]
11 info lifecycle dicegame@0.1.0~start: Failed to exec start script
12 silly lifecycle dicegame@0.1.0~start: Returned: code: -4058 signal: null
13 info lifecycle dicegame@0.1.0~start: Failed to exec start script
14 verbose stack Error: dicegame@0.1.0 start: `react-scripts start`
14 verbose stack spawn C:\Program Files\Git\bin\bash.exe ENOENT
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
14 verbose stack at onErrorNT (internal/child_process.js:469:16)
14 verbose stack at processTicksAndRejections (internal/process/task_queues.js:84:21)
15 verbose pkgid dicegame@0.1.0
16 verbose cwd C:\Users\rickb\Desktop\Coding\portfolio\diceGame\dicegame
17 verbose Windows_NT 10.0.18363
18 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
19 verbose node v12.16.2
20 verbose npm v6.14.4
21 error code ELIFECYCLE
22 error syscall spawn C:\Program Files\Git\bin\bash.exe
23 error file C:\Program Files\Git\bin\bash.exe
24 error path C:\Program Files\Git\bin\bash.exe
25 error errno ENOENT
26 error dicegame@0.1.0 start: `react-scripts start`
26 error spawn C:\Program Files\Git\bin\bash.exe ENOENT
27 error Failed at the dicegame@0.1.0 start script.
27 error This is probably not a problem with npm. There is likely additional logging output above.
28 verbose exit [ 1, true ]
Пожалуйста, помогите, большое спасибо.