Read the statement by Michael Teeuw here.
Error EBADENGINE when installing MM v2.28.0
-
Hello!
I have issues updating my MagicMirror to the current version 2.28.0.When I run npm install I get this error message:
mirror@raspberrypi:~/MagicMirror $ sudo npm run install-mm > magicmirror@2.28.0 install-mm > 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: magicmirror@2.28.0 npm error notsup Not compatible with your version of node/npm: magicmirror@2.28.0 npm error notsup Required: {"node":">=20"} npm error notsup Actual: {"npm":"10.8.1","node":"v18.17.1"} npm error A complete log of this run can be found in: /root/.npm/_logs/2024-08-04T16_49_26_116Z-debug-0.logseems easy to solve, but I absolutely fail to bring my node to the required version.
using nvm current I get this answer:
mirror@raspberrypi:~/MagicMirror $ nvm current v20.16.0Edit: this is what happens if I try and install node via n:
mirror@raspberrypi:~ $ sudo n lts installing : node-v20.16.0 mkdir : /usr/local/n/versions/node/20.16.0 fetch : https://nodejs.org/dist/v20.16.0/node-v20.16.0-linux-arm64.tar.xz copying : node/20.16.0 /usr/bin/n: Zeile 746: /usr/local/bin/node: Datei oder Verzeichnis nicht gefunden installed : (with npm 10.8.1)so it should work… PLEASE help!
-
@Ix ONE… NEVER EVER use sudo for MM commands, EVER…
once you do that then you HAVE to use SUDO for a lot of things you don’t want to give root permissions
note node and npm are not MM commands
SO, you had to upgrade node and npm for this release BEFORE doing the upgrade
see https://forum.magicmirror.builders/topic/18836/v2-28-0OR, you could have run the upgrade command from my scripts repo
see https://github.com/sdetweil/MagicMirror_scriptsfor node version, check (not what nvm thinks)
node -vmy scripts use the tool n, which is nvm written in javascript…
-
first: thanks for answering so fast!
node -v gives this:
mirror@raspberrypi:~ $ node -v v20.16.0this is also the version I installed via n
nevertheless, the wrong version is recognized when trying npm i -
@Ix how about npm -v
-
mirror@raspberrypi:~ $ npm -v 10.8.1 -
-
@sdetweil said in Error EBADENGINE when installing MM v2.28.0:
npm run install-mm
mirror@raspberrypi:~/MagicMirror $ npm run install-mm > magicmirror@2.28.0 install-mm > 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: magicmirror@2.28.0 npm error notsup Not compatible with your version of node/npm: magicmirror@2.28.0 npm error notsup Required: {"node":">=20"} npm error notsup Actual: {"npm":"10.8.1","node":"v18.17.1"} npm error A complete log of this run can be found in: /root/.npm/_logs/2024-08-04T17_53_51_013Z-debug-0.log -
@Ix said in Error EBADENGINE when installing MM v2.28.0:
/root/.npm/_logs/2024-08-04T17_53_51_013Z-debug-0.log
ok, it thinks you are running npm as root… probably cause of some sudo somwhere…
show results of
whoami cd ~/MagicMirror ls -laF -
@sdetweil
whoamimirror@raspberrypi:~/MagicMirror $ whoami mirrorand ls in MM directory:
mirror@raspberrypi:~/MagicMirror $ ls -laF insgesamt 688 drwxr-xr-x 18 mirror mirror 4096 4. Aug 17:48 ./ drwxr-xr-x 26 mirror mirror 4096 3. Jul 09:30 ../ -rw-r--r-- 1 mirror mirror 83743 4. Aug 17:48 CHANGELOG.md drwxr-xr-x 2 mirror mirror 4096 3. Apr 17:11 clientonly/ -rw-r--r-- 1 mirror mirror 1617 3. Apr 17:11 Collaboration.md drwxr-xr-x 2 mirror mirror 4096 4. Aug 17:48 config/ drwxr-xr-x 2 mirror mirror 4096 3. Apr 17:11 css/ -rw-r--r-- 1 mirror mirror 10244 2. Jul 21:56 .DS_Store -rw-r--r-- 1 mirror mirror 238 2. Okt 2023 .editorconfig -rw-r--r-- 1 mirror mirror 27 3. Apr 17:11 .eslintignore -rw-r--r-- 1 mirror mirror 3020 3. Apr 17:11 .eslintrc.json drwxr-xr-x 3 mirror mirror 4096 4. Aug 17:48 fonts/ drwxr-xr-x 8 mirror mirror 4096 4. Aug 20:28 .git/ -rw-r--r-- 1 mirror mirror 1034 2. Okt 2023 .gitattributes drwxr-xr-x 3 mirror mirror 4096 3. Apr 17:11 .github/ -rw-r--r-- 1 mirror mirror 1140 3. Apr 17:11 .gitignore drwxr-xr-x 3 mirror mirror 4096 3. Apr 17:11 .husky/ -rw-r--r-- 1 mirror mirror 3103 2. Okt 2023 index.html drwxr-xr-x 2 mirror mirror 4096 4. Aug 19:18 installers/ -rw-r--r-- 1 mirror mirror 1096 2. Okt 2023 jest.config.js drwxr-xr-x 2 mirror mirror 4096 4. Aug 17:48 js/ -rw-r--r-- 1 mirror mirror 264 2. Okt 2023 jsconfig.json -rw-r--r-- 1 mirror mirror 1098 3. Apr 17:11 LICENSE.md -rw-r--r-- 1 mirror mirror 6947 3. Apr 17:11 mm2.png drwxr-xr-x 13 mirror mirror 4096 3. M?r 11:49 modules/ -rw-r--r-- 1 mirror mirror 1130 2. Okt 2023 module-types.ts drwxr-xr-x 414 root root 28672 3. Apr 17:16 node_modules/ -rw-r--r-- 1 mirror mirror 48 3. Apr 17:11 .npmrc -rw-r--r-- 1 mirror mirror 3694 4. Aug 17:48 package.json -rw-r--r-- 1 mirror mirror 414176 4. Aug 17:48 package-lock.json -rw-r--r-- 1 mirror mirror 96 3. Apr 17:11 .prettierignore -rw-r--r-- 1 mirror mirror 29 2. Okt 2023 .prettierrc.json -rw-r--r-- 1 mirror mirror 3279 3. Apr 17:11 README.md drwxr-xr-x 2 mirror mirror 4096 3. Apr 17:11 serveronly/ drwxr-xr-x 2 mirror mirror 4096 2. Okt 2023 splashscreen/ -rw-r--r-- 1 mirror mirror 126 2. Okt 2023 .stylelintrc.json drwxr-xr-x 8 mirror mirror 4096 4. Jan 2024 tests/ drwxr-xr-x 2 mirror mirror 4096 3. Apr 17:11 translations/ drwxr-xr-x 4 mirror mirror 4096 4. Aug 17:48 vendor/ -
@Ix said in Error EBADENGINE when installing MM v2.28.0:
drwxr-xr-x 414 root root 28672 3. Apr 17:16 node_modules/
my only guess
SO, lets try
cd ~/MagicMirror # using sudo here only to remove the root owned folder sudo rm -rf node_modules npm run install-mm -
I deleted node_modules directory as recommended and after that, this is what happened:
mirror@raspberrypi:~/MagicMirror $ npm run install-mm > magicmirror@2.28.0 install-mm > 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: magicmirror@2.28.0 npm error notsup Not compatible with your version of node/npm: magicmirror@2.28.0 npm error notsup Required: {"node":">=20"} npm error notsup Actual: {"npm":"10.8.2","node":"v18.18.0"} npm error A complete log of this run can be found in: /home/mirror/.npm/_logs/2024-08-04T20_08_34_045Z-debug-0.logNow it says it’s running on node v18.18.0 instead of v18.17.1 but still not v20.16 which is installed. I don’t get it at all…
-
@Ix wild… never seen this.
SO, i would use nvm and n to remove all the added node versions…
get back to whatever before…
exit the shell window and open againverify still on the prior nodejs
then use n version_number
sudo n 20.9
verify that is correct node -v
the close shell and open again,
verify nodethen try the npm run install-mm again
-
@sdetweil said in Error EBADENGINE when installing MM v2.28.0:
@Ix wild… never seen this.
SO, i would use nvm and n to remove all the added node versions…
done
get back to whatever before…
exit the shell window and open againdone
verify still on the prior nodejs
then use n version_number
sudo n 20.9
verify that is correct node -v
the close shell and open again,
verify nodewell, now there’s another problem:
mirror@raspberrypi:~ $ sudo n 20.9 copying : node/20.9.0 /usr/bin/n: Zeile 746: /usr/local/bin/node: Datei oder Verzeichnis nicht gefunden installed : (with npm 10.1.0) mirror@raspberrypi:~ $ node -v -bash: /usr/local/bin/node: Datei oder Verzeichnis nicht gefundenSry for German: it’s “no such file or directory”
then try the npm run install-mm again
-
@Ix do
which node
Then
sudo rm $(which node)
Then
hash -r
which node
and again
Then node -v -
okay done all that, node is completely gone from my machine. I guess, reinstalling it would be the next step?
-
@Ix rename the MagicMirror folder and run my install script
-
@Ix then rename new out and old back in and do the npm run install-mm
-
Tried that, but the script failed. I have attached the install.log
install starting - Mon Aug 5 18:37:16 CEST 2024 installing on aarch64 processor system the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye total used free shared buff/cache available Mem: 1849 228 1116 30 504 1527 Swap: 2047 0 2047 [96mUpdating packages ...[0m Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Hit:3 https://deb.nodesource.com/node_18.x bullseye InRelease Reading package lists... apt-get update completed ok Reading package lists... Building dependency tree... Reading state information... pv is already the newest version (1.6.6-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. apt-get upgrade started apt-get upgrade result =rc=0 Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [96mInstalling helper tools ...[0m Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.9). curl is already the newest version (7.74.0-1.3+deb11u12). git is already the newest version (1:2.30.2-1+deb11u2). unzip is already the newest version (6.0-26+deb11u1). wget is already the newest version (1.21-1+deb11u1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. node not installed, trying via apt-get Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package nodejs:armv7l E: Unable to locate package npm:armv7l npm not installed, trying via apt-get npm installed now, install n Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libnode72 : Conflicts: nodejs-legacy nodejs : Conflicts: npm E: Unable to correct problems, you have held broken packages. installing on bullseye [92mnode failed to execute, please check the error message and resolve before trying again[0m install aborted - Mon Aug 5 18:37:59 CEST 2024 -
@Ix do node -v
-
@sdetweil said in Error EBADENGINE when installing MM v2.28.0:
@Ix do node -v
mirror@raspberrypi:~ $ node -v bash: node: command not found
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login