Outdated "Downloading and installing Node.js and npm"

[MikeMcC399]

Situation

URL: https://docs.npmjs.com/downloading-and-installing-node-js-and-npm
Title: Downloading and installing Node.js and npm
Source page: https://github.com/npm/documentation/blob/main/content/getting-started/configuring-your-local-environment/downloading-and-installing-node-js-and-npm.mdx

The page separately links to

• https://nodejs.org/en/download/
• https://nodejs.org/en/download/package-manager/

The https://nodejs.org/en/download/ has however been substantially changed and the old https://nodejs.org/en/download/package-manager/ page no longer exists.

Instead https://nodejs.org/en/download/package-manager/ redirects to https://nodejs.org/en/download/.

The version managers recommended on https://nodejs.org/en/download/ differ from the ones recommended by the npm docs.

Edit: Removed the table attempting to summarize https://nodejs.org/en/download/ as it appears to be too dynamic to keep up with.

Also the page refers to the outdated term "OS X". This was rebranded in 2016 to "macOS" with the Sierra release - see https://en.wikipedia.org/wiki/MacOS. Edit: fixed

Suggestions

• npm should decide whether it wants to keep its own suggestions or align with Node.js suggestions for Node.js version managers
• Separate links to the https://nodejs.org/en/download/package-manager/ should be removed / consolidated to use only the active https://nodejs.org/en/download/ page
• Rename "OS X" references to "macOS"

[MikeMcC399]

• docs: rebrand OS X references to macOS cli#8371 submitted to rebrand from OS X to macOS

[MikeMcC399]

https://docs.npmjs.com/downloading-and-installing-node-js-and-npm

remains confusing to read, as it treats https://nodejs.org/en/download/package-manager/ like it still exists

Nobody has picked up this issue so far, so I may make an attempt at some improvement above what I already submitted under PR npm/cli#8371

[MikeMcC399]

• The URL https://nodejs.org/en/download/package-manager/ used to contains package manager instructions, however it now redirects to https://nodejs.org/en/download where a subset of this information is available

• The previous contents were last seen https://web.archive.org/web/20240318015303/https://nodejs.org/en/download/package-manager/ on Mar 18, 2024

• There is no longer a section corresponding to "Less-common operating systems". https://nodejs.org/en/download/package-manager/ currently limits itself to:

  • Windows
  • macOS
  • Linux
  • AIX

• PR docs: remove reference to Node.js download less common os cli#8418 submitted to be able to tick off one more of the sub-issues here

[MikeMcC399]

https://docs.npmjs.com/downloading-and-installing-node-js-and-npm (website only page) is out of date and out of sync with
https://docs.npmjs.com/cli/v11/configuring-npm/install which has been updated

I'm afraid that I was confused about these two pages and how they are related, so I only caused https://docs.npmjs.com/cli/v11/configuring-npm/install to be updated

It looks like https://docs.npmjs.com/cli/v11/configuring-npm/install

from source file
https://github.com/npm/cli/blob/latest/docs/lib/content/configuring-npm/install.md

needs to be manually merged into the source file
https://github.com/npm/documentation/blob/main/content/getting-started/configuring-your-local-environment/downloading-and-installing-node-js-and-npm.mdx

Or would there be a better way to ensure that the content only has to be maintained in one place?