Upgrade

plainbroke

@sdetweil
Do I need 22.22.1 or 22.22.2 ???
When I updated with your script I got 22.21.1 for node is that correct?

sdetweil

@plainbroke the package.json says 22.21.1 or above, not 23.
My script installs 22.21.1 or slightly higher

So you should be fine

mumblebaj

@sdetweil Hi Sam. Apologies for the late reply. See below.

mble@pi:~ $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"

$$\      $$\                     $$\           $$\      $$\ $$\                                          $$$$$$\
$$$\    $$$ |                    \__|          $$$\    $$$ |\__|                                        $$  __$$\
$$$$\  $$$$ | $$$$$$\   $$$$$$\  $$\  $$$$$$$\ $$$$\  $$$$ |$$\  $$$$$$\   $$$$$$\   $$$$$$\   $$$$$$\  \__/  $$ |
$$\$$\$$ $$ | \____$$\ $$  __$$\ $$ |$$  _____|$$\$$\$$ $$ |$$ |$$  __$$\ $$  __$$\ $$  __$$\ $$  __$$\  $$$$$$  |
$$ \$$$  $$ | $$$$$$$ |$$ /  $$ |$$ |$$ /      $$ \$$$  $$ |$$ |$$ |  \__|$$ |  \__|$$ /  $$ |$$ |  \__|$$  ____/
$$ |\$  /$$ |$$  __$$ |$$ |  $$ |$$ |$$ |      $$ |\$  /$$ |$$ |$$ |      $$ |      $$ |  $$ |$$ |      $$ |
$$ | \_/ $$ |\$$$$$$$ |\$$$$$$$ |$$ |\$$$$$$$\ $$ | \_/ $$ |$$ |$$ |      $$ |      \$$$$$$  |$$ |      $$$$$$$$\
\__|     \__| \_______| \____$$ |\__| \_______|\__|     \__|\__|\__|      \__|       \______/ \__|      \________|
                       $$\   $$ |
                       \$$$$$$  |
                        \______/

install log being saved to /home/mumble/install.log
Updating packages ...
Installing helper tools ...
nvm_command is sudo n 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.21.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.9.4
Installed npm version: V10.9.4
No npm upgrade necessary.
Cloning MagicMirror ...
Cloning into 'MagicMirror'...
remote: Enumerating objects: 509, done.
remote: Counting objects: 100% (509/509), done.
remote: Compressing objects: 100% (406/406), done.
remote: Total 509 (delta 118), reused 319 (delta 93), pack-reused 0 (from 0)
Receiving objects: 100% (509/509), 572.14 KiB | 9.54 MiB/s, done.
Resolving deltas: 100% (118/118), done.
Cloning MagicMirror Done!
Installing dependencies ...
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"}
npm notice
npm notice New major version of npm available! 10.9.4 -> 11.18.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.18.0
npm notice To update run: npm install -g npm@11.18.0
npm notice
npm error A complete log of this run can be found in: /home/mumble/.npm/_logs/2026-07-04T07_32_18_929Z-debug-0.log
Unable to install dependencies!

I had to manually install v22.22.2 before I could install MM.

mumblebaj

@sdetweil Yeah, I saw that so not sure where that 22.22.2 came from but it was there as can bee seen in the previous post. I had to install 22.22.2 and then only would MM install. Was weird.

As for the SD card failure, I don’t know why this is but when I upgraded in April the card failed. When I upgraded now the first time the card failed so I had to setup a new one again.

sdetweil

@mumblebaj yes, wierd… I just opened the project on github
picked package.json on the master branch

"engines": {
		"node": ">=22.21.1 <23 || >=24"
	}

develop branch says the same

karsten13

the eslint-plugin-package-json dependency has this requirement but this is only a devDependency so a normal install without devDependencies should not trigger this error.

		"node_modules/eslint-plugin-package-json": {
			"version": "1.5.0",
			"resolved": "https://registry.npmjs.org/eslint-plugin-package-json/-/eslint-plugin-package-json-1.5.0.tgz",
			"integrity": "sha512-KQkAdn+7I4vn1W4Va+V8M94RhcgZBvgrxMglDqgEhJgQDRUJ9RdtrEiHoe/84oVTIlp0jiPttLYwkExdvHYhZQ==",
			"dev": true,
			"license": "MIT",
			"dependencies": {
				"@altano/repository-tools": "^2.0.1",
				"change-case": "^5.4.4",
				"detect-indent": "^7.0.2",
				"detect-newline": "^4.0.1",
				"eslint-fix-utils": "~0.4.1",
				"eslint-json-compat-utils": "^0.2.3",
				"jsonc-eslint-parser": "^3.1.0",
				"package-json-validator": "^1.5.0",
				"semver": "^7.7.3",
				"sort-object-keys": "^2.0.0",
				"sort-package-json": "^4.0.0"
			},
			"engines": {
				"node": "^22.22.2 || >=24.15.0"
			},
			"peerDependencies": {
				"@eslint/json": ">=1.0.0",
				"eslint": ">=9.0.0"
			},
			"peerDependenciesMeta": {
				"@eslint/json": {
					"optional": true
				}
			}
		},

sdetweil

@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

karsten13

@sdetweil

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…