Read the statement by Michael Teeuw here.
Blackscreen after update to v.2.8.0
-
I can, should I run that from the config file?
I will say though that it worked before the upgrade and I tried the config.js.sample file and it didnt work.
-
@potts-mike - Run it from the command line in the
/home/pi/MagicMirror
folder. -
THe config file does not contain syntax errors.
pi@raspberrypi:~/MagicMirror $ npm run config:check > magicmirror@2.8.0 config:check /home/pi/MagicMirror > node tests/configs/check_config.js Checking file... /home/pi/MagicMirror/config/config.js Your configuration file doesn't contain syntax errors :) pi@raspberrypi:~/MagicMirror $
-
@potts-mike ok, then do
npm start dev
Or
Ctrl-shift-i if already running
And in the developers window, select the console tab, and scroll up to find any errors. Red text usually.
-
I know that the last thing it says it is launching the app but a white screen with the developer console opens with the error “Dev tools was disconnected from the page…”
pi@raspberrypi:~/MagicMirror $ npm start dev > magicmirror@2.8.0 start /home/pi/MagicMirror > sh run-start.sh "dev" Starting MagicMirror: v2.8.0 Loading config ... Loading module helpers ... WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'node_helper' Loading module helpers ... App threw an error during load Error: Cannot find module 'node_helper' at Module._resolveFilename (internal/modules/cjs/loader.js:602:15) at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12) at Function.Module._load (internal/modules/cjs/loader.js:528:25) at Module.require (internal/modules/cjs/loader.js:658:17) at require (internal/modules/cjs/helpers.js:20:18) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-Sonos/node_helper.js:7:18) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-Sonos/node_helper.js:30:3) at Module._compile (internal/modules/cjs/loader.js:711:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10) at Module.load (internal/modules/cjs/loader.js:620:32) Whoops! There was an uncaught exception... { Error: Cannot find module 'node_helper' at Module._resolveFilename (internal/modules/cjs/loader.js:602:15) at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12) at Function.Module._load (internal/modules/cjs/loader.js:528:25) at Module.require (internal/modules/cjs/loader.js:658:17) at require (internal/modules/cjs/helpers.js:20:18) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-Sonos/node_helper.js:7:18) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-Sonos/node_helper.js:30:3) at Module._compile (internal/modules/cjs/loader.js:711:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10) at Module.load (internal/modules/cjs/loader.js:620:32) code: 'MODULE_NOT_FOUND' } MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues Launching application.
-
@potts-mike i get the same with the pi4, the npm installs on some modules are killing the mirror. i think its safe to link all of these threads into one, ive put out a request for the dev of one module, i have no idea if any other module that i will put on the mirror will do the same i can only take it one step at a time, the affected module is mmm-nest-status.
pi@raspberrypi:~ $ cd MagicMirror/modules pi@raspberrypi:~/MagicMirror/modules $ git clone https://github.com/BenRoe/MMM-SystemStats Cloning into 'MMM-SystemStats'... remote: Enumerating objects: 22, done. remote: Counting objects: 100% (22/22), done. remote: Compressing objects: 100% (14/14), done. remote: Total 231 (delta 10), reused 16 (delta 8), pack-reused 209 Receiving objects: 100% (231/231), 88.08 KiB | 578.00 KiB/s, done. Resolving deltas: 100% (122/122), done. pi@raspberrypi:~/MagicMirror/modules $ cd MMM-SystemStats pi@raspberrypi:~/MagicMirror/modules/MMM-SystemStats $ npm install npm notice created a lockfile as package-lock.json. You should commit this file. added 1 package from 1 contributor and audited 1 package in 1.265s found 0 vulnerabilities pi@raspberrypi:~/MagicMirror/modules/MMM-SystemStats $ cd pi@raspberrypi:~ $ cd MagicMirror pi@raspberrypi:~/MagicMirror $ npm run config:check > magicmirror@2.8.0 config:check /home/pi/MagicMirror > node tests/configs/check_config.js Checking file... /home/pi/MagicMirror/config/config.js Your configuration file doesn't contain syntax errors :) pi@raspberrypi:~/MagicMirror $ cd modules pi@raspberrypi:~/MagicMirror/modules $ git clone https://github.com/michael5r/mmm-nest-status.git Cloning into 'mmm-nest-status'... remote: Enumerating objects: 135, done. remote: Total 135 (delta 0), reused 0 (delta 0), pack-reused 135 Receiving objects: 100% (135/135), 65.27 KiB | 718.00 KiB/s, done. Resolving deltas: 100% (77/77), done. pi@raspberrypi:~/MagicMirror/modules $ cd mmm-nest-status pi@raspberrypi:~/MagicMirror/modules/mmm-nest-status $ npm install npm WARN deprecated undefined@0.1.0: this package has been deprecated npm WARN saveError ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/package.json' npm notice created a lockfile as package-lock.json. You should commit this file. 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. removed 1 package in 1.141s found 0 vulnerabilities pi@raspberrypi:~/MagicMirror/modules/mmm-nest-status $ cd pi@raspberrypi:~ $ pm2 restart MagicMirror Use --update-env to update environment variables [PM2] Applying action restartProcessId on app [MagicMirror](ids: 0) [PM2] [MagicMirror](0) ✓ ┌─────────────┬────┬──────┬────────┬───┬─────┬──────────┐ │ Name │ id │ mode │ status │ ↺ │ cpu │ memory │ ├─────────────┼────┼──────┼────────┼───┼─────┼──────────┤ │ MagicMirror │ 0 │ fork │ online │ 2 │ 0% │ 2.5 MB │ └─────────────┴────┴──────┴────────┴───┴─────┴──────────┘ Use `pm2 show <id|name>` to get more details about an app pi@raspberrypi:~ $ npm run config:check 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-07-13T20_08_21_703Z-debug.log
-
@dazza120 mmm-nest-status does not have a package.json file,
so you should NOT do an npm install in that modules folder -
@sdetweil ok interesting any idea why it kills it if you do that as it’s never before very strange thanks I’ll take a look at it
-
@dazza120 no idea… all this npm stuff is new to me and I don’t understand all the rules and issues
-
@sdetweil 100% that man it doesn’t need npm install and is working :) thank you