Read the statement by Michael Teeuw here.
v2.18.0 update gave black screen, then nothing.
-
@richard238 said in v2.18.0 update gave black screen, then nothing.:
Error when getting information for file “/home/pi/MagicMirror/config/config.js”
you need to copy from save
cd ~/MagicMirror.save/config cp -p config.js ~/Magicmirror/config
-
Good morning Sam.
Tried that late yesterday, and yes, it works.
And this morning, I copiedcustom.css
from
/home/pi/MagicMirror.save/css
to
/home/pi/MagicMirror/css
This too is working perfectly.
Is there anything else to do, housekeeping maybe, or is that it now?
-
@richard238 if everything is running ok then I think you are done, and can delete the
MagicMirror.save folder -
Ok, I’ll do that then.
Do we know what the cause of all this was, was it something to do with a mismatch in versions of node and npm?
-
@richard238 no idea what caused it.
there clearly was an error somewhere in the upgrade process, maybe reported and missed, or unreported.
but can u send me the MagicMirror.save/installers/upgrade.log
-
That’s a huge file, what’s the best way to send it?
-
@richard238 use zip to make it smaller
do
cd ~ zip logfile.zip ~/MagicMirror.save/installers/upgrade.log # rename logfile.zip so it can be emailed mv logfile.zip logfile.txt
then use email to send logfile.txt to me.
same userid at gmail -
-
@richard238 thx…
looking back thru the topic, the
Module.createRequire is not a function is because of downlevel node.
the eslint library depends on node 14+ for that to work.
(from npm run config:check) -
@richard238 if you haven’t deleted yet, can u try something
because you did
pi@magicmirror:~/MagicMirror $ npm init -y
in the mm folder, instead of the module folder, this overwrote the shipped package.json
so,
do
cd ~/MagicMirror.save git checkout package.json rm -rf node_modules rm package.lock.json npm install --only=prod
then stop good mm if running and then do , in the MagicMirror.save folder
npm start