updated installer script available for testing

sdetweil

I have submitted these changes under pull request 1789

mrdenmark

i’ve tried running this installer a couple of times now but i keep getting the message-unable to install dependencies-any suggestions on how to proceed?

sdetweil

@mrdenmark show me the install.log from the MagicMirror folder… email to me if cannot post…

email userid is same as here on gmail

mrdenmark

[0_1571974919417_install.log](Uploading 100%)

mrdenmark

email sent,

sdetweil

@mrdenmark thanks… can u try

cd ~/MagicMirror
rm -rf node_modules
npm install

please advise results

Newbie007

Hey, it worked for me thanks!

mrdenmark

no joy for me,heres a copy of the terminal output-
pi@raspberrypi:~/MagicMirror $ rm -rf node_modules
pi@raspberrypi:~/MagicMirror $ npm install
npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.
npm WARN acorn-jsx@5.1.0 requires a peer of acorn@^6.0.0 || ^7.0.0 but none is installed. You must install peer dependencies yourself.

npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /home/pi/MagicMirror/node_modules/jsesc/bin/jsesc
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod ‘/home/pi/MagicMirror/node_modules/jsesc/bin/jsesc’
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2019-10-25T19_15_39_049Z-debug.log
pi@raspberrypi:~/MagicMirror $ DISPLAY=:0 npm start

magicmirror@2.9.0 start /home/pi/MagicMirror
sh run-start.sh

run-start.sh: 7: run-start.sh: electron: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! magicmirror@2.9.0 start: sh run-start.sh
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the magicmirror@2.9.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! /home/pi/.npm/_logs/2019-10-25T19_16_09_123Z-debug.log
pi@raspberrypi:~/MagicMirror $ ^C
pi@raspberrypi:~/MagicMirror $

any suggestions?
many thanks for your help so far!

mrdenmark

heres the debug log-

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/local/bin/node’, ‘/usr/local/bin/npm’, ‘start’ ]
2 info using npm@6.12.0
3 info using node@v12.13.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.9.0~prestart: magicmirror@2.9.0
6 info lifecycle magicmirror@2.9.0~start: magicmirror@2.9.0
7 verbose lifecycle magicmirror@2.9.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.9.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle magicmirror@2.9.0~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.9.0~start: Args: [ ‘-c’, ‘sh run-start.sh’ ]
11 info lifecycle magicmirror@2.9.0~start: Failed to exec start script
12 verbose stack Error: magicmirror@2.9.0 start: sh run-start.sh
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:210:5)
12 verbose stack at maybeClose (internal/child_process.js:1021:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
13 verbose pkgid magicmirror@2.9.0
14 verbose cwd /home/pi/MagicMirror
15 verbose Linux 4.19.75-v7+
16 verbose argv “/usr/local/bin/node” “/usr/local/bin/npm” “start”
17 verbose node v12.13.0
18 verbose npm v6.12.0
19 error code ELIFECYCLE
20 error syscall spawn
21 error file sh
22 error errno ENOENT
23 error magicmirror@2.9.0 start: sh run-start.sh
23 error spawn ENOENT
24 error Failed at the magicmirror@2.9.0 start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

sdetweil

@mrdenmark great info! Let me research this