Read the statement by Michael Teeuw here.
Issue with latest update
-
Hi there, this is my first time posting. I appreciate any help in advance. I updated MagicMirror, MMM-Wallpaper, and MMM-CalendarExt2 and my mirror stopped loading. :-(
When I ran “git pull && npm run install-mm”, I got the following error:
hint: Pulling without specifying how to reconcile divergent branches is hint: discouraged. You can squelch this message by running one of the following hint: commands sometime before your next pull: hint: hint: git config pull.rebase false # merge (the default strategy) hint: git config pull.rebase true # rebase hint: git config pull.ff only # fast-forward only hint: hint: You can replace "git config" with "git config --global" to set a default hint: preference for all repositories. You can also pass --rebase, --no-rebase, hint: or --ff-only on the command line to override the configured default per hint: invocation. Already up to date. > magicmirror@2.28.0 install-mm > npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev npm ERR! code EBADENGINE npm ERR! engine Unsupported engine npm ERR! engine Not compatible with your version of node/npm: @eslint/eslintrc@3.1.0 npm ERR! notsup Not compatible with your version of node/npm: @eslint/eslintrc@3.1.0 npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"} npm ERR! notsup Actual: {"npm":"10.1.0","node":"v20.8.0"} npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-07-25T21_39_18_726Z-debug-0.log
Then, tried updating node using “sudo apt install node” and I end up with v20.8.0. I can’t seem to get to the required node version.
-
@sdetweil I was able to resolve the issue by updating my node to v20.16.0 via the following:
https://nodejs.org/en/download/package-managerThen, I ran the recommended update command and it worked — I’m up and running!
Thank you!
-
@ttguru can you do
git status
in the MagicMirrorso we can see what files of ours are changed
once we resolve that,
use my upgrade script to update, use
force
instead of
applysee
https://github.com/sdetweil/MagicMirror_scriptsit will upgrade node as well
-
@sdetweil I was able to resolve the issue by updating my node to v20.16.0 via the following:
https://nodejs.org/en/download/package-managerThen, I ran the recommended update command and it worked — I’m up and running!
Thank you!
-
@ttguru ok, you didn’t need to update node manually… the script would have done it…
but I was more concerned with the modified MM files…(which should never happen)
-