Read the statement by Michael Teeuw here.
Wish i never updated to 2.7.1 Black Screen!
-
I have no clue what happened to this during the git pull all i get is a black screen i really don’t want to install everything from scratch it was working good before apart from the electron memory leak, i take it that electron was autoMagically installed with the latest MM version. Help Please, see log
pi@raspberrypi:~ $ npm start dev npm ERR! path /home/pi/package.json npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall open npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 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-04-02T20_51_53_518Z-debug.log
Debug Log Below
0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start', 'dev' ] 2 info using npm@6.4.1 3 info using node@v10.15.3 4 verbose config Skipping project config: /home/pi/.npmrc. (matches userconfig) 5 verbose stack Error: ENOENT: no such file or directory, open '/home/pi/package.json' 6 verbose cwd /home/pi 7 verbose Linux 4.14.98-v7+ 8 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" "dev" 9 verbose node v10.15.3 10 verbose npm v6.4.1 11 error path /home/pi/package.json 12 error code ENOENT 13 error errno -2 14 error syscall open 15 error enoent ENOENT: no such file or directory, open '/home/pi/package.json' 16 error enoent This is related to npm not being able to find a file. 17 verbose exit [ -2, true ]
-
@dazza120 said in Wish i never updated to 2.7.1 Black Screen!:
pi@raspberrypi:~ $ npm start dev
you need to
cd MagicMirror
THEN do the
npm start dev
-
@sdetweil hi thanks but when I do that I’m greated with a white screen that says the dev screen has disconnected and would reload, the pi is just totally locked after that, only powering it down would can get it back to where I can use terminal again :(
-
@dazza120 ok, after the git pull, u have to do npm install again in the mm folder
Mm is short for MagicMirror
-
@sdetweil done that some folders didn’t like that though kept coming up with errors, think I’m going to have to reinstall it from scratch :(
-
@dazza120 slow down
What errors. Let’s work thru ut
-
@sdetweil hi mate im getting this from MMM-pages
npm WARN MMM-pages No repository field. npm WARN MMM-pages No license field. audited 275 packages in 6.448s found 0 vulnerabilities
and this from mmm-hue-lights and a couple of others
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/package.json' npm WARN enoent ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/package.json' npm WARN modules No description npm WARN modules No repository field. npm WARN modules No README data npm WARN modules No license field. audited 1 package in 1.465s found 0 vulnerabilities
-
hue-lights doesn’t have a package.json, so no npm install there
npm WARN MMM-pages No repository field.
npm WARN MMM-pages No license field.package.json doesn’t have some typically useful fields… no problems
so, one thing to try also is
npm start &
which will start MM AND give u back the terminal window…
I get lots of messages as things start up there…
-
@sdetweil this is what i get
npm start & [1] 1352 pi@raspberrypi:~ $ npm ERR! path /home/pi/package.json npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall open npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 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-04-02T22_38_46_083Z-debug.log
-
@dazza120 said in Wish i never updated to 2.7.1 Black Screen!:
pi@raspberrypi
but u have to start in MagicMirror folder
cd ~/MagicMirror
npm start &