Upgrade

karsten13

so a normal install without devDependencies should not trigger this error

I wrote “should”, didn’t test it and this was my expectation to node behavior …

As node seems to check all dependencies, we need >= 22.22.2, we can edit release notes and forum post if needed …

sdetweil

@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

sdetweil

@karsten13 fixed the release notes

karsten13

@sdetweil I did it on github, will write a test for this so that we see it prior to release

mumblebaj

@sdetweil No worries. I will check tomorrow after work and downgrade node and install again. Will advise

sdetweil

@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

mumblebaj

@sdetweil Just ran it quickly and it seems like it installed 22.22.2

mumble@pi:~ $ sudo n
     copying : node/22.21.1
   installed : v22.21.1 (with npm 10.9.4)
mumble@pi:~ $ node -v
v22.21.1
mumble@pi:~ $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
update log will be in /home/mumble/MagicMirror/installers/upgrade.log
doing test run = false
Node currently installed. Checking version number.
Minimum Node version: v22.22.2
Installed Node version: v22.21.1
installing correct version of node and npm, please wait
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v22.21.1
Installed Node version: v22.22.2
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.9.7
Installed npm version: V10.9.7
No npm upgrade necessary.


upgrading from version 2.37.0 to 2.37.0
force: line 762: pm2: command not found
some node app still running, please shutdown those apps, maybe MagicMirror, and restart
here is a list of those processes

msimon360

@sdetweil Just and FYI, I just tried a fresh install and got the same issue with node.
marksimon@digiframe:~ $ git clone https://github.com/MagicMirrorOrg/MagicMirror.git
Cloning into ‘MagicMirror’…
remote: Enumerating objects: 31023, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 31023 (delta 2), reused 2 (delta 2), pack-reused 31018 (from 2)
Receiving objects: 100% (31023/31023), 26.41 MiB | 2.15 MiB/s, done.
Resolving deltas: 100% (19515/19515), done.
marksimon@digiframe:~ $ cd MagicMirror/
marksimon@digiframe:~/MagicMirror $ node --run install-mm
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.21.1”}

Then I tried using the script and it installed node v22.22.2 and looks like it is working.
marksimon@digiframe:~/MagicMirror $ bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” force
update log will be in /home/marksimon/MagicMirror/installers/upgrade.log
doing test run = false
Node currently installed. Checking version number.
Minimum Node version: v22.22.2
Installed Node version: v22.21.1
installing correct version of node and npm, please wait
Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v22.21.1
Installed Node version: v22.22.2

sdetweil

@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

mumblebaj

@sdetweil I see some major changes coming down the line for npm v12.

https://github.blog/changelog/2026-07-08-npm-install-time-security-and-gat-bypass2fa-deprecation/

sdetweil

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

mumblebaj

@sdetweil Yeah, warnings come from 11.16.0+

sdetweil

@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…