NPM problem "EBADENGINE" which I fail to solve

sdetweil · Jul 2, 2024, 5:23 PM

@Ix says require 18.18.0 current 18.17.1

so I would do

node -v
hash -r
node -v

Ix · Jul 2, 2024, 6:09 PM

Hello @sdetweil and thank you for your fast answer!

I tried and pasted your commands in my terminal. Sadly, it didn’t work…
Here’s what it says:

mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ node -v
hash -r
node -v 
v18.18.0
v18.18.0
mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ sudo npm ci
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@stylistic/eslint-plugin@2.1.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@stylistic/eslint-plugin-js@2.1.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'eslint-visitor-keys@4.0.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@stylistic/eslint-plugin-jsx@2.1.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@typescript-eslint/utils@7.9.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@stylistic/eslint-plugin-ts@2.1.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@typescript-eslint/utils@7.9.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@typescript-eslint/scope-manager@7.9.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@typescript-eslint/types@7.9.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@typescript-eslint/typescript-estree@7.9.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@typescript-eslint/visitor-keys@7.9.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'espree@10.0.1',
npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'eslint-visitor-keys@4.0.0',
npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
npm warn EBADENGINE }

> mmm-publictransporthafas@2.1.1 prepare
> [ -f node_modules/.bin/husky ] && husky || echo husky is not installed.


added 436 packages, and audited 437 packages in 43s

155 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

It’s as if it doesn’t recognize my used version of node…

MMRIZE · Jul 2, 2024, 6:10 PM

@Ix
Install recent nodejs.
I don’t know how you have installed the current version of nodejs. So I cannot give you an exact advice.
Generally I prefer to manage node version with nvm

Ix · Jul 2, 2024, 6:14 PM

@MMRIZE said in NPM problem "EBADENGINE" which I fail to solve:

Install recent nodejs.
I don’t know how you have installed the current version of nodejs. So I cannot give you an exact advice.

Hey @MMRIZE 👋

I used the following command:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash

which I found here

this is “nvm” isn’t it?

sdetweil · Jul 2, 2024, 6:16 PM

@MMRIZE 1st line of 1st included message image shows his nvm command

says using 18.18.0

the npm ci says using 18.17.1

try npm i

I use n, which is a nodejs version of nvm

sudo mpn install n

n version
n list
n --help

Ix · Jul 2, 2024, 6:19 PM

@sdetweil said in NPM problem "EBADENGINE" which I fail to solve:

try npm I

also tried this. same result :-/

Ix · Jul 2, 2024, 6:23 PM

@sdetweil said in NPM problem "EBADENGINE" which I fail to solve:

I use n, which is a nodejs version of nvm

sudo mpn install n

n version
n list

I also tried this.
Here are the results:

mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ n list
node/22.2.0
mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ n version

  Error: invalid version 'version'

sdetweil · Jul 2, 2024, 6:33 PM

@Ix version is the one you want to use

n 18

n 18.18

need sudo to change, as it write to /usr/local/bin which is protected
(as as nvm does)

see
n --help

Ix · Jul 2, 2024, 6:40 PM

@sdetweil

I already tried and changed my used version to v18.18 via nvm (what obviously didn’t work)

Now I installed “n” and tried again with your method.
Here are the results:

mirror@raspberrypi:~/MagicMirror/modules $ sudo n 18.18
  installing : node-v18.18.2
       mkdir : /usr/local/n/versions/node/18.18.2
       fetch : https://nodejs.org/dist/v18.18.2/node-v18.18.2-linux-arm64.tar.xz
     copying : node/18.18.2
/usr/bin/n: Zeile 746: /usr/local/bin/node: Datei oder Verzeichnis nicht gefunden
   installed :  (with npm 9.8.1)

There is an error: “Datei oder Verzeichnis nicht gefunden” which translates into “File or directory not found” (Sry for my German OS 😅)

so there is another issue

sdetweil · Jul 2, 2024, 6:52 PM

@Ix said in NPM problem "EBADENGINE" which I fail to solve:

/usr/local/n/versions/node/18.18.2

does that directory exist?

I’ve never had any problem with n, on windows, linux or mac.

do a

which node

so we can see where it is coming from