Read the statement by Michael Teeuw here.
Blank screen with error in terminal upon start.
-
@dcarls91 if u added back modules, did u check and run npm install in the module folders where they had a package.json file?
if you do npm start from a terminal window, you might get some error messages…
I would go back to the base config.js and start adding one module at a time…
-
@sdetweil I will do that. I went into all of my modules and and ran npm install as well
-
It may also be an electron issue
-
@dcarls91 I’m not sure if what you did was right.
For me the best way and proven a hundred times is:
- sit at an external device (laptop/PC)
- SSH into the mirror
npm start dev
- open the mirror’s page on a browser on the laptop/PC (http://IP.OF.THE.MIRROR:8080)
- check the shell console (where you did the npm start dev) as well as the developer’s console of the browser for errors.
There will be something that will help you find the error
-
@dcarls91 said in Blank screen with error in terminal upon start.:
I went into all of my modules and and ran npm install as well
IF they do NOT have a package.json file as part of a module, then there is a bad side effect or a required file beging deleted
you can check
cd ~/MagicMirror ls modules/node_modules/node_helper/index.js
if the file is there, all good,
if not do thiscd ~/MagicMirror git checkout modules/node_modules/node_helper/index.js