Open
Description
Hi,
not sure what the best solution is, so I didn't create a PR right away.
When creating a new asteroid for uptime kuma I noticed the guide seems out of date.
In step 2 for the prerequisites it says to run npm install npm@latest -g
Which results in this output:
[hrms01@mirfac ~]$ npm install npm@latest -g
npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: [email protected]
npm error notsup Not compatible with your version of node/npm: [email protected]
npm error notsup Required: {"node":"^20.17.0 || >=22.9.0"}
npm error notsup Actual: {"npm":"10.8.2","node":"v18.20.6"}
npm error A complete log of this run can be found in: /home/hrms01/.npm/_logs/2025-03-26T08_23_50_366Z-debug-0.log
While it should be:
+ [email protected]
added 169 packages from 86 contributors, removed 157 packages and updated 45 packages in 22.432s
or similar.
Switching to node 20 does fix this and npm install npm@latest -g
works:
[hrms01@mirfac ~]$ uberspace tools version use node 20
Selected Node.js version 20
The new configuration is adapted immediately. Minor updates will be applied automatically.
[hrms01@mirfac ~]$ npm install npm@latest -g
added 1 package in 7s
24 packages are looking for funding
run `npm fund` for details
but now uptime kuma warns me about using an unsupported npm version:
HEAD is now at 5bb329fa Update to 1.23.16
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@azure/[email protected]',
npm warn EBADENGINE required: { node: '10 || 12 || 14 || 16 || 18' },
npm warn EBADENGINE current: { node: 'v20.18.3', npm: '11.2.0' }
npm warn EBADENGINE }
It does work eventually, but it's not ideal.
Looks to me like the installed NPM Version is too new to update Node 18?
Metadata
Metadata
Assignees
Labels
No labels