Repository navigation
Handling of deprecated / hidden commands hydrate & prepare #624
Description
Issue
-
The following commands are hidden since PR Refactoring of the CLI interface #291 implemented RFC: New command names (and alias the old ones) #274 in release corepack@0.20.0:
corepack hydratecorepack prepare
These commands:
- are not documented in the README
- have no migration guide to their replacement commands
- do not appear in the output of
corepack --help - are described in the output of
corepack hydrate --helpandcorepack prepare --help - 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 v18v22 & v23 describes instead corepack use / corepack install. Edit: v22 and v24 documentation now have no detailed content.)
Suggestion
- Describe the above commands as deprecated and either add
thea migration tablefrom RFC: New command names (and alias the old ones) #274to 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. - Extend the help text for the commands to indicate that they are deprecated.
- 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
Activity
MikeMcC399 commentedon Mar 17, 2025
I would like to submit a PR to add a migration table to the README. As a first pass to creating the table it would look like this:
corepack hydrate path/to/archive.tgzcorepack install -g --cache-only path/to/archive.tgzcorepack hydrate path/to/archive.tgz --activatecorepack install -g path/to/archive.tgzcorepack prepare foo@1.2.3corepack install -g --cache-only foo@1.2.3corepack prepare foo@1.2.3 --activatecorepack install -g foo@1.2.3corepack prepare -o ...corepack pack -o ...Is this something that maintainers would welcome to have added to the
README?For consistency,
--cache-onlyshould probably also be added to the corepack install <-g,--global> [... name[@]] section as an option as well.MikeMcC399 commentedon Mar 21, 2025
MikeMcC399 commentedon Mar 23, 2025
Edit: I closed this PR after there was no response
MikeMcC399 commentedon Apr 17, 2025
trivikr commentedon Apr 18, 2025
There is not new release Node.js 18.x planned AFAIK.
This is based on a skeet from active releaser when v18.20.8 was released.
The future versions of 20.x and 22.x will get the decision in bold and call to action added in nodejs/node#57825
MikeMcC399 commentedon Apr 18, 2025
@trivikr
Thanks for the research! According to the table in nodejs/Release#737, I also would not expect any 18.x release after
v18.20.8. Edit: Node.js 18 is now end-of-life and the last Node.js 18 release was indeedv18.20.8I will be watching for the future Node.js releases, although by now I have removed any links I originally had in any documentation / code that point to Corepack on the Node.js site, so my content shouldn't be impacted anymore anyway.
wwuck commentedon Mar 9, 2026
Can the website https://corepack.org get updated for the new commands documentation?
MikeMcC399 commentedon Mar 9, 2026
@wwuck
This GitHub repo is the place where you should be getting your information. https://corepack.org contains outdated & irrelevant information. It is not owned by the nodejs organization and it should be ignored.