updated installer script available for testing

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

sdetweil

@mrdenmark said in Anyone want to try updated installer...:

2 info using npm@6.12.0
3 info using node@v12.13.0

can you do

sudo npm i -g npm

the try the npm install from the MagicMirror folder
also, show me the output of uname -a
what OS is this?

i don’t have node_modules/jsec installed either, but no error…

sdetweil

@mrdenmark i am installing in text mode OS… first time… will report

mrdenmark

@sdetweil

terminal output below of everything i just tried,uname at the bottom.
do you want the debug logs pasting?

pi@raspberrypi:~/MagicMirror $ sudo npm i 0g npm
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for 0g

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-10-26T03_33_41_912Z-debug.log
pi@raspberrypi:~/MagicMirror $ cd
pi@raspberrypi:~ $ sudo npm i 0g npm
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for 0g

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-10-26T03_34_31_151Z-debug.log

pi@raspberrypi:~ $ cd ~/MagicMirror
pi@raspberrypi:~/MagicMirror $ npm install
npm WARN tarball cached data for json5@^2.1.0 (sha512-l+3HXD0GEI3huGq1njuqtzYK8OYJyXMkOLtQ53pjWh89tvWS2h6l+1zMkYWqlb57+SiQodKZyvMEFb2X+KrFhQ==) seems to be corrupted. Refreshing cache.
npm WARN tarball cached data for jsesc@^2.5.1 (sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==) seems to be corrupted. Refreshing cache.

magicmirror@2.9.0 install /home/pi/MagicMirror
cd vendor && npm install

npm WARN tarball cached data for is-extendable@0.1.1 (sha1-YrEQ4omkcUGOPsNqYX1HLjAd/Ik=) seems to be corrupted. Refreshing cache.
npm WARN tarball cached data for lcid@1.0.0 (sha1-MIrMr6C8SDo4Z7S28rlQYlHRuDU=) seems to be corrupted. Refreshing cache.
npm WARN tarball cached data for minimatch@3.0.4 (sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==) seems to be corrupted. Refreshing cache.
npm WARN tarball cached data for invert-kv@1.0.0 (sha1-EEqOSqym09jNFXqO+L+rLXo//bY=) seems to be corrupted. Refreshing cache.
npm WARN tarball cached data for os-locale@1.4.0 (sha1-IPnxeuKe00XoveWDsT0gCYA8FNk=) seems to be corrupted. Refreshing cache.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“arm”})

added 82 packages from 56 contributors and audited 220 packages in 204.709s
found 5 vulnerabilities (4 low, 1 high)
run npm audit fix to fix them, or npm audit for details

magicmirror@2.9.0 postinstall /home/pi/MagicMirror
sh untrack-css.sh && sh installers/postinstall/postinstall.sh && npm run install-fonts

MagicMirror installation successful!

magicmirror@2.9.0 install-fonts /home/pi/MagicMirror
cd fonts && npm install

added 1 package from 1 contributor and audited 1 package in 25.735s
found 0 vulnerabilities

added 50 packages from 51 contributors, removed 7 packages, updated 10 packages, moved 1 package and audited 3714 packages in 543.232s
found 29 vulnerabilities (1 low, 1 moderate, 27 high)
run npm audit fix to fix them, or npm audit for details
pi@raspberrypi:~/MagicMirror $ 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-26T03_48_33_404Z-debug.log
pi@raspberrypi:~/MagicMirror $ cd
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux
pi@raspberrypi:~ $

mrdenmark

i never thought to mention it before but i have MM working on a windows laptop-i’ve been playing around with it while i waited for all my parts to arrive-are there any files that i can copy between the 2 machines to fix the problem?

sdetweil

@mrdenmark said in Anyone want to try updated installer...:

sudo npm i 0g npm

oops… I miss typed

sudo npm i -g npm
then lets erase the node_modules folder again
rm -rf node_modules
then
npm install

i don’t like the ‘seems to be corrupted’
maybe some problem with the memory card?