@plainbroke got em

@plainbroke I dont know, can you send me the ~/MagicMirror/installers/upgrade.log

Or open an issue in the repo and attach it there

@plainbroke I’m guessing the library the module uses is now down level from what MagicMirror is using

I see you opened an issue., I don’t see any trouble logging in the module.

Does anything show up in the pm2 logs?

this was a bug in backup and restore when multiple ‘module’ folders were sourced from the same git repo (multi- instance copy type problem)

the two scripts are fixed now… if you used these scripts, please run another backup to make sure the module_list file is updated…

@MyMirror can you provide me the

~/MagicMirror/installlers/restore.log

open an issue and attach it there

In the issue. Please explain the steps you used up to restore

edit
| thanks… see it

@p1lspeda said:

npm install electron@43.1.0

I opened issue on the MMM-Fuel repo
https://github.com/fewieden/MMM-Fuel/issues/128

@p1lspeda awesome!!

second module impacted…

@p1lspeda ah, node-fetch… there is an electron bug in the 2.37 version of Electron

do this
stop MagicMirror

cd ~/MagicMirror
npm install electron@43.1.0

start MagicMirror

please advise

@Redicaljk there is an open issue, on the module repo… looks like Gasbuddy removed the api the module used

@p1lspeda best to open and issue on the module github page to engage the module author, most don’t visit the forum often

@fischi87 awesome

@mumblebaj on windows these were NOT warnings… I actually had to run different tasks to get the scripts allowed/approved… I hadn’t expected that in npm 11…

same problem as always, some scammers leveraged the automation tools to do damage and now we all have to pay for it…

@mumblebaj yeh, I was working on a mobile app last weekend
It had npm 11 installed ( windows) and had all the acceptscript problems

@msimon360 said:

Just and FYI, I just tried a fresh install and got the same issue with node.

yes, you didn’t use the install script you did it manually

@rkorell also it’s a newish feature. Used not to allow issues on forks

@thartley you can mark it solved

find the post that best describes the fix,
click the 3 dot bottom right, click mark this post as the correct answer

@mumblebaj if you have nvm or n installed (I detect nvm, install n )

do this

sudo n

it might give you a list, then pick the right one 22.21.1

if not there, then

sudo n 22.21.1

to install it

@karsten13 fixed the release notes

@karsten13 bummer… I fixed this is a prior release of something, renamed the devdependencies: entry and then there was nothing to check… what a pita

fixed my scripts…

@mumblebaj

can you rerun, set node back…
sudo n 22.21.1

then run upgrade again with force to allow install over the same version

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force

worked for me… thanks for the heads up

@karsten13 when I run

npm run install-mm I get the dev error, even tho it specifies no dev

> npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: eslint-plugin-package-json@1.5.0
npm error notsup Not compatible with your version of node/npm: eslint-plugin-package-json@1.5.0
npm error notsup Required: {"node":"^22.22.2 || >=24.15.0"}
npm error notsup Actual:   {"npm":"10.9.4","node":"v22.22.1"}
npm error A complete log of this run can be found in: /home/sam/.npm/_logs/2026-07-06T17_12_27_381Z-debug-0.log