From 0881058dfa6a3ee396839c315e51901e1977de70 Mon Sep 17 00:00:00 2001 From: William Entriken Date: Thu, 25 Sep 2025 15:13:00 -0400 Subject: [PATCH 1/2] Update Corepack installation instructions Clarified the opt-in status of Corepack and noted its removal from future Node.js releases. --- packages/docusaurus/docs/getting-started/extra/corepack.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docusaurus/docs/getting-started/extra/corepack.mdx b/packages/docusaurus/docs/getting-started/extra/corepack.mdx index d8353b034f49..022cac7b6ede 100644 --- a/packages/docusaurus/docs/getting-started/extra/corepack.mdx +++ b/packages/docusaurus/docs/getting-started/extra/corepack.mdx @@ -18,7 +18,7 @@ Corepack is marked experimental so we can iterate on its CLI faster, but it's al ## Installation -Corepack is included with all official Node.js releases starting from Node.js 14.19 / 16.9. It's however opt-in for the duration of the experimental stage, so you'll need to run `corepack enable` before it's active. +Corepack is included with all official Node.js releases starting from Node.js 14.19 / 16.9. It's however opt-in, so you'll need to run `corepack enable` before it's active. Also, this [will be removed](https://socket.dev/blog/node-js-tsc-votes-to-stop-distributing-corepack) from Node.js releases starting with Node.js 25+ You can quickly check whether Corepack is enabled by running `yarn exec env | grep COREPACK_ROOT`: if you get a path as output, Corepack is properly installed. If not, something may be messing with how the shims are installed. In that case check the [Troubleshooting](/corepack#troubleshooting) section for advices. From dd24967ef56598683c998d8f96bd74f2ac703f34 Mon Sep 17 00:00:00 2001 From: William Entriken Date: Thu, 25 Sep 2025 15:23:44 -0400 Subject: [PATCH 2/2] Link to authoritative source Updated the link regarding Corepack removal from Node.js releases. --- packages/docusaurus/docs/getting-started/extra/corepack.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docusaurus/docs/getting-started/extra/corepack.mdx b/packages/docusaurus/docs/getting-started/extra/corepack.mdx index 022cac7b6ede..2e3e4c89b9e0 100644 --- a/packages/docusaurus/docs/getting-started/extra/corepack.mdx +++ b/packages/docusaurus/docs/getting-started/extra/corepack.mdx @@ -18,7 +18,7 @@ Corepack is marked experimental so we can iterate on its CLI faster, but it's al ## Installation -Corepack is included with all official Node.js releases starting from Node.js 14.19 / 16.9. It's however opt-in, so you'll need to run `corepack enable` before it's active. Also, this [will be removed](https://socket.dev/blog/node-js-tsc-votes-to-stop-distributing-corepack) from Node.js releases starting with Node.js 25+ +Corepack is included with all official Node.js releases starting from Node.js 14.19 / 16.9. It's however opt-in, so you'll need to run `corepack enable` before it's active. Also, this [will be removed](https://github.com/nodejs/TSC/pull/1697#issuecomment-2737093616) from Node.js releases starting with Node.js 25+ You can quickly check whether Corepack is enabled by running `yarn exec env | grep COREPACK_ROOT`: if you get a path as output, Corepack is properly installed. If not, something may be messing with how the shims are installed. In that case check the [Troubleshooting](/corepack#troubleshooting) section for advices.