EBADENGINE npm error eslint/espree - MMM-EarthquakeAlerts

UncleRoger

My Mirror was down for a while and when I booted it up again, I had some updates to do. These included MMM-EarthquakeAlerts and MMM-BackgroundSlideshow.

I did a “git pull” and “npm install” for MMM-BackgroundSlideshow and it seemed fine. I did the same for MMM-Traffic and again, it seemed fine. Then I did it for MMM-EarthquakeAlerts and got a bunch of messages after the “npm install” saying “EBADENGINE”:

npm install
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@eslint/config-array@0.23.2',
npm WARN EBADENGINE   required: { node: '^20.19.0 || ^22.13.0 || >=24' },
npm WARN EBADENGINE   current: { node: 'v20.9.0', npm: '10.1.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@eslint/config-helpers@0.5.2',
npm WARN EBADENGINE   required: { node: '^20.19.0 || ^22.13.0 || >=24' },
npm WARN EBADENGINE   current: { node: 'v20.9.0', npm: '10.1.0' }
npm WARN EBADENGINE }

and so on. There are a total of 11 sets, all for “@eslint/something” except the last which just says "espree@11.1.1’ for the package.

I think that I need to update node.js to at least version 20.19 but I’m not sure how to do that. I honestly have no idea how I installed it in the first place except that it was probably via Sam’s excellent scripts?

If anyone has any suggestions on how to fix this, I’d really appreciate it. I found that I’ve really come to rely on it.

UncleRoger

@sdetweil

Thank you! I think that fixed it.

sdetweil

@UncleRoger can you check for either tool?

n
Or
nvm
See if either responds
Or get not found

My upgrade script would have tried to redo npm install for the modules after upgrading node

UncleRoger

@sdetweil

nvm was not found but n was – it gave me the option to install 20.8.0 or 20.9.0 so I picked the latter and got a whole lot of “cannot remove” errors. That’s the version I have currently.

So should I use the upgrade script or have I mucked it up too much for that?

sdetweil

@UncleRoger n stores in the /usr folder, so you have to use sudo for that

sudo n 20.9

UncleRoger

@sdetweil

Thank you! I think that fixed it.