Hi.
After trying 3 more times, I finally installed it :).
It may be good for noobs like myself, to specify that you have to "cd <directory>" to where you have the SogeBot folder (I was trying to do npm install <directory>).
But sadly, I now have the issue of the follwing bug report :
After trying 3 more times, I finally installed it :).
It may be good for noobs like myself, to specify that you have to "cd <directory>" to where you have the SogeBot folder (I was trying to do npm install <directory>).
But sadly, I now have the issue of the follwing bug report :
0 info it worked if it ends with ok
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' ]
2 info using npm@3.10.10
3 info using node@v6.10.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle sogebot@1.4.4~prestart: sogebot@1.4.4
6 silly lifecycle sogebot@1.4.4~prestart: no script for prestart, continuing
7 info lifecycle sogebot@1.4.4~start: sogebot@1.4.4
8 verbose lifecycle sogebot@1.4.4~start: unsafe-perm in lifecycle true
9 verbose lifecycle sogebot@1.4.4~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\Gregorif\Desktop\Twitch\SogeBot-1.4.4\node_modules\.bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\nodejs\;C:\Users\Gregorif\AppData\Roaming\npm
10 verbose lifecycle sogebot@1.4.4~start: CWD: C:\Users\Gregorif\Desktop\Twitch\SogeBot-1.4.4
11 silly lifecycle sogebot@1.4.4~start: Args: [ '/d /s /c',
11 silly lifecycle 'npm run copy:dist && node --harmony-async-await ./main' ]
12 silly lifecycle sogebot@1.4.4~start: Returned: code: 9 signal: null
13 info lifecycle sogebot@1.4.4~start: Failed to exec start script
14 verbose stack Error: sogebot@1.4.4 start: `npm run copy:dist && node --harmony-async-await ./main`
14 verbose stack Exit status 9
14 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:886:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid sogebot@1.4.4
16 verbose cwd C:\Users\Gregorif\Desktop\Twitch\SogeBot-1.4.4
17 error Windows_NT 6.1.7601
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
19 error node v6.10.1
20 error npm v3.10.10
21 error code ELIFECYCLE
22 error sogebot@1.4.4 start: `npm run copy:dist && node --harmony-async-await ./main`
22 error Exit status 9
23 error Failed at the sogebot@1.4.4 start script 'npm run copy:dist && node --harmony-async-await ./main'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the sogebot package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error npm run copy:dist && node --harmony-async-await ./main
23 error You can get information on how to open an issue for this project with:
23 error npm bugs sogebot
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls sogebot
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]