Add Fresh support for Node.js 18 (with npm 9)
Closed, ResolvedPublicFeature
Actions

Assigned To

Authored By

	Tgr
	May 28 2023, 9:17 AM

Description

rollup.js (used in GrowthExperiments for bundling a lightweight version of d3) requires npm 8+, Fresh currently has npm 7 (Node.js v16.19.1 (npm 7.21.0)).

Details

Related Changes in Gerrit:

	Subject	Repo	Branch	Lines +/-
	update fresh-node16, add fresh-node18, add fresh-node20	fresh	master	+462 -2

Customize query in gerrit

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Resolved	Feature	Krinkle	T337647 Add Fresh support for Node.js 18 (with npm 9)
		Resolved		Jdforrester-WMF	T331181 Create WMF CI images and jobs for Node.js 18

Event Timeline

Tgr created this task.May 28 2023, 9:17 AM

Restricted Application added projects: Growth-Team, Performance-Team. · View Herald TranscriptMay 28 2023, 9:17 AM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Can be worked around by using

fresh-node -- npm install -g --prefix ./custom-npm npm

and then writing custom-npm/bin/npm instead of npm but it's somewhat annoying.

Fresh follows WMF CI. WMF CI is meant to follow upstream Node.js packages, of which the npm pairings can be found at https://nodejs.org/en/download/releases.

We used to maintain a custom package for npm but I stopped doing that at npm version 7.21, with the idea to follow upstream instead.

When we upgraded CI from Node 12 to Node 14, we re-activated our package override to prevent a messy downgrade because upstream Node.js 14 shipped with npm 6, and our custom package was already ahead at npm version 7. I left a comment in the code so that when we upgrade CI to Node.js 16, we don't continue this override.

node14: Update from bundled npm 6 to pinned npm 7
https://gerrit.wikimedia.org/r/c/integration/config/+/723256
T267888, T267889

When the Node 16 upgrade took place for CI last year (https://gerrit.wikimedia.org/r/c/integration/config/+/813930), however, we kept the override. @Jdforrester-WMF found that the npm/npx commands from upstream were "non-operable".

Note that @kostajh reported the same rollup.js requirement with npm 8 at T314470#8636102. And WMDE has also reported this in relation to another packate at T330380.

I suggest we repurpose this task in favour of following T331181: Create WMF CI images and jobs for Node.js 18, and make sure to actually remove the override there in favour of Node.js 18's bundled npm package, which will be npm 9.

Krinkle renamed this task from Support npm 8 in Fresh to Add Fresh support for Node.js 18 (with npm 9).May 28 2023, 2:53 PM

Krinkle added a subtask: T331181: Create WMF CI images and jobs for Node.js 18.

In T337647#8885497, @Krinkle wrote:

I suggest we repurpose this task in favour of following T331181: Create WMF CI images and jobs for Node.js 18, and make sure to actually remove the override there in favour of Node.js 18's bundled npm package, which will be npm 9.

WFM.

kostajh moved this task from Inbox to Triaged on the Growth-Team board.Jun 1 2023, 8:57 AM

Krinkle changed the task status from Open to Stalled.Jun 6 2023, 3:18 PM

Krinkle triaged this task as Medium priority.

Krinkle moved this task from Inbox, needs triage to Backlog: Maintenance, non-prioritized on the Performance-Team board.

Sgs subscribed.Jun 13 2023, 9:27 AM

Krinkle removed a project: Performance-Team.Jul 21 2023, 12:55 AM

Krinkle mentioned this in T256626: Refactor WebdriverIO tests from sync to async mode.Aug 2 2023, 3:13 PM

Jdforrester-WMF changed the status of subtask T331181: Create WMF CI images and jobs for Node.js 18 from Stalled to In Progress.Aug 8 2023, 4:24 PM

Jdforrester-WMF closed subtask T331181: Create WMF CI images and jobs for Node.js 18 as Resolved.Aug 8 2023, 4:32 PM

Change 946991 had a related patch set uploaded (by Krinkle; author: Krinkle):

[fresh@master] update fresh-node16, add fresh-node18, add fresh-node20