Handling of deprecated / hidden commands `hydrate` & `prepare`

Issue

• The following commands are hidden since PR https://github.com/nodejs/corepack/pull/291 implemented https://github.com/nodejs/corepack/issues/274 in release corepack@0.20.0:

  • corepack hydrate
  • corepack prepare

These commands:

1. are not documented in the README
2. have no migration guide to their replacement commands
3. do not appear in the output of corepack --help
4. are described in the output of corepack hydrate --help and corepack prepare --help
5. neither their usage, nor their help text indicates that the commands are deprecated

Several issues lately have shown users reporting problems when executing corepack prepare.

corepack prepare is listed as a valid command in Node.js documentation Corepack latest v18 Edit: Node.js 18 is now in end-of-life status, so documentation should no longer be referred to. (Node.js v20, v22 & v23 describes instead corepack use / corepack install. Edit: v22 and v24 documentation now have no detailed content.)

Suggestion

1. Describe the above commands as deprecated and either add the a migration table from https://github.com/nodejs/corepack/issues/274 to the README or create a separate Migration Guide document. Edit: the migration table in the PR contains inaccuracies and cannot be used as it stands.
2. Extend the help text for the commands to indicate that they are deprecated.
3. Output a deprecation warning if deprecated commands are used.

Also review Node.js documentation Corepack latest v18 and initiate an update if possible. Edit: Node.js 18 has passed into end-of-life status, so all related assets are now frozen.

Related Node.js documentation

• Node.js 18 Corepack (Node.js 18 is end-of-life)
• Node.js 20 Corepack
• Node.js 22 Corepack
• Node.js 24 Corepack
• Node.js latest Corepack

Start with the README and the existing corepack hydrate --help and corepack prepare --help output. Review the command-related documentation and help text for the deprecated commands, then define completion as documenting their status and migration path, marking the help output accordingly, and adding the requested deprecation warning if the relevant entry points are identified.