Uh oh!
There was an error while loading. Please reload this page.
doc: clarify Corepack removal in v25+ - #57813
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ljharb
left a comment
There was a problem hiding this comment.
LGTM with the grammar suggestion
aduh95
commented
Apr 10, 2025
The commit message do not match our guidelines, the first word after the subsystem should be an imperative verb. |
Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com>
f163dc7 to
3b95127Comparetrivikr
commented
Apr 10, 2025
@aduh95 I've updated the first commit to use imperative verb after subsystem: |
Uh oh!
There was an error while loading. Please reload this page.
Closing this PR, as the existing documentation can be edited better with highlight and call to action just like it's done for other modules for all Node.js versions. That PR is posted in #57825 |
trivikr
commented
Apr 10, 2025
I'll post a new PR specific to v25.x after #57825 is merged. |
trivikr
commented
Apr 14, 2025
We're instead trying to enable redirect from corepack latest documentation in nodejs/nodejs.org#7643 (review) |
Alternative to #57663
This preserves the existing documentation page for corepack which has backlinks from all over the internet.
It can be removed close to April 2028, after corepack is completely removed from all Node.js versions.
Refs: