Bug 32309

Summary:	Cannot manually update npm using npm install -g npm@latest because node 18.7.0 and above is needed
Product:	Mageia	Reporter:	Kristoffer Grundström <lovaren>
Component:	RPM Packages	Assignee:	christian barranco <chb0>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal
Version:	9
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	nodejs-18.16.1-2.mga9.src.rpm	CVE:
Status comment:
Bug Depends on:	32176, 32341
Bug Blocks:

Description Kristoffer Grundström 2023-09-21 14:59:57 CEST

Description of problem: I see a message running npm install when building tutanota-desktop that there's a new npm version available.

Running npm install -g npm@latest gives me the following error:

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@10.1.0
npm ERR! notsup Not compatible with your version of node/npm: npm@10.1.0
npm ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
npm ERR! notsup Actual:   {"npm":"9.5.1","node":"v18.16.1"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kristoffer/.npm/_logs/2023-09-21T12_48_21_411Z-debug-0.log

node -v shows:
v18.16.1

npm -v shows:
9.5.1

Version-Release number of selected component (if applicable): v18.16.1

How reproducible: All the time when trying to update.

Steps to Reproduce:
1. Install npm and nodejs with urpmi or dnf.
2. Run npm install -g npm@latest.
3. Update will fail.

Comment 1 Lewis Smith 2023-09-21 21:12:05 CEST

Thank you for the report.
Is your system up-to-date? We have had version: 18.17.1 in Cauldron for 5 weeks, 
so you should have got it then. Perhaps it got stuck in M9 version freeze.

Assigning to squidf who updates nodejs.

Source RPM: npm => nodejs-18.16.1-2.mga9.src.rpm
Assignee: bugsquad => chb0

Comment 2 christian barranco 2023-09-21 21:24:47 CEST

Hi

With the error:
npm ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}

It looks like you need nodejs (>=18.17.0 and <19.0.0) or >=20.5.0

18.17.1 has been somehow stuck in core/updates_testing. It is now validated by QA and you should get it soon as an update.
If you cannot wait, get it from core/updates_testing.

Depends on: (none) => 32176

Comment 3 Kristoffer Grundström 2023-09-21 21:41:50 CEST

(In reply to Lewis Smith from comment #1)
> Thank you for the report.
> Is your system up-to-date? We have had version: 18.17.1 in Cauldron for 5
> weeks, 
> so you should have got it then. Perhaps it got stuck in M9 version freeze.
> 
> Assigning to squidf who updates nodejs.

Even though I love Cauldron when it's updated frequently I prefer to only use Core release and Core updates on it so having an update in Updates Testing.

I'll have to wait until it gets moved to Core Updates I guess.

Marja Van Waes 2023-09-28 18:47:28 CEST

Depends on: (none) => 32341

Comment 4 katnatek 2024-02-22 02:04:53 CET

Still valid?
we have nodejs-18.18.2-1.mga9 and nodejs-18.19.1-1.mga9 is waiting to be validated

Comment 5 christian barranco 2024-02-23 13:54:45 CET

It looks like it depends on other bug reports which have been fixed, but this report has not been closed automatically. I close it.

Resolution: (none) => FIXED
Status: NEW => RESOLVED