Bug: recommened node and npm versions seem out of sync

[jpmcb]

Describe the bug

Per the docs:

In order to run the project we need the following software binaries installed on our development machines: node>=18.15.0 npm>=9.6.3

but the latest LTS version of node 18 (v18.16.1) comes with npm v9.5.1.

https://nodejs.org/en/download

Maybe this needs to be updated? Or is it expected users should have a newer out-of-band version of npm from their node version?

Steps to reproduce

N/a

Browsers

No response

Additional context (Is this in dev or production?)

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[jpmcb]

Hmmmm seems like attempting npm ci with the older version didn't work anyways (given the restriction in the engines field of the package.json. Upgrading to the newest npm works.

[MartiinWalsh]

Also, the package.json specifies "node": ">= 16.19.1".

Should we update the package.json to require Node version 18.15.0 or later to match the documentation.

Alternatively, revise the documentation to match the package.json, stating that the project requires Node version 16.19.1 or later.