Error EBADENGINE when installing MM v2.28.0

sdetweil

@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

Ix

@sdetweil

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.log

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

sdetweil

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

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 node

then try the npm run install-mm again

Ix

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

done

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 node

well, 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 gefunden

Sry for German: it’s “no such file or directory”

then try the npm run install-mm again

sdetweil

@Ix do

which node
Then
sudo rm $(which node)
Then
hash -r
which node
and again
Then node -v

Ix

@sdetweil

okay done all that, node is completely gone from my machine. I guess, reinstalling it would be the next step?

sdetweil

@Ix rename the MagicMirror folder and run my install script

sdetweil

@Ix then rename new out and old back in and do the npm run install-mm

Ix

@sdetweil

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

sdetweil

@Ix do node -v