A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
Won't start on windows after upgrade...
-
0 info it worked if it ends with ok 1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli 'C:\\Users\\John\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'start' ] 2 info using npm@3.10.9 3 info using node@v6.9.1 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle magicmirror@2.1.1~prestart: magicmirror@2.1.1 6 silly lifecycle magicmirror@2.1.1~prestart: no script for prestart, continuing 7 info lifecycle magicmirror@2.1.1~start: magicmirror@2.1.1 8 verbose lifecycle magicmirror@2.1.1~start: unsafe-perm in lifecycle true 9 verbose lifecycle magicmirror@2.1.1~start: PATH: C:\Users\John\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\MagicMirror\node_modules\.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Calibre2\;C:\Program Files\nodejs\;C:\xampp\php;C:\ProgramData\ComposerSetup\bin;C:\Program Files\Git\cmd;C:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\John\AppData\Local\Microsoft\WindowsApps;C:\Users\John\AppData\Roaming\npm;C:\Users\John\AppData\Roaming\Composer\vendor\bin 10 verbose lifecycle magicmirror@2.1.1~start: CWD: C:\MagicMirror 11 silly lifecycle magicmirror@2.1.1~start: Args: [ '/d /s /c', 'sh run-start.sh' ] 12 silly lifecycle magicmirror@2.1.1~start: Returned: code: 1 signal: null 13 info lifecycle magicmirror@2.1.1~start: Failed to exec start script 14 verbose stack Error: magicmirror@2.1.1 start: `sh run-start.sh` 14 verbose stack Exit status 1 14 verbose stack at EventEmitter. (C:\Users\John\AppData\Roaming\npm\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. (C:\Users\John\AppData\Roaming\npm\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:877:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) 15 verbose pkgid magicmirror@2.1.1 16 verbose cwd C:\MagicMirror 17 error Windows_NT 10.0.14393 18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\John\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start" 19 error node v6.9.1 20 error npm v3.10.9 21 error code ELIFECYCLE 22 error magicmirror@2.1.1 start: `sh run-start.sh` 22 error Exit status 1 23 error Failed at the magicmirror@2.1.1 start script 'sh run-start.sh'. 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 magicmirror package, 23 error not with npm itself. 23 error Tell the author that this fails on your system: 23 error sh run-start.sh 23 error You can get information on how to open an issue for this project with: 23 error npm bugs magicmirror 23 error Or if that isn't available, you can get their info via: 23 error npm owner ls magicmirror 23 error There is likely additional logging output above. 24 verbose exit [ 1, true ]
-
Okay if you install git bash from here: https://git-for-windows.github.io/
Will not work under windows terminal [command window - cmd] window. Install program then right click on desktop and you will see a “Git Bash Here” on that menu. Type your normal ‘npm start’ and the mirror will run.
Windows does not recognize bash or sh… under git bash it does because it creates a linux like enviroment and runs great.
Thanks Strawberry… again.