NPM problem "EBADENGINE" which I fail to solve

Ix

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

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

yes I think:

mirror@raspberrypi:~/MagicMirror/modules $ cd /usr/local/bin
mirror@raspberrypi:/usr/local/bin $ ls
corepack  node  npm  npx

node is colored green in this ls

sdetweil

@Ix note its NOT usr/local/BIN its usr/local/N
(uppercase fore emphasis here)

Ix

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

@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

here is the result from “a”:

mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ n -a

  Error: missing -a|--arch value

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

@Ix note its NOT usr/local/BIN its usr/local/N
(uppercase fore emphasis here)

yeah, but see the error message I posted above: it seems to get the directory wrong as well. sry for me being a newbie in this case

I really appreciate you helping me here!

edit:
file is there:

mirror@raspberrypi:/usr/local/n/versions/node $ ls
18.18.2  22.2.0

sdetweil

@Ix no

do

which node

this will tell the path to the first executable it finds

on my pi4 with node (from n)
is says

which node
/usr/local/bin/node

on my x64 box with n 18
it says

which node
/usr/local/bin/node

Ix

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

@Ix no

do
which node
this will tell the path to the first executable it finds

ah I over read that.

here’s the result:

mirror@raspberrypi:/usr/local/n/versions/node $ which node
/home/mirror/.nvm/versions/node/v18.18.0/bin/node

well that’s a completely different path… so what should I do now?

sdetweil

@Ix the module author says this is a bug in the lint checker…

do this, in the module folder

npm i @stylistic/eslint-plugin@1.8.1

then npm install

Ix

@sdetweil

THANK YOU! This did it, the module is working again, finally!

You are the best 🙌

/solved

sdetweil

@Ix not me… another user