1<!DOCTYPE html> 2<html lang="en"> 3<head> 4 <meta charset="utf-8"> 5 <meta name="viewport" content="width=device-width"> 6 <meta name="nodejs.org:node-version" content="v14.21.2"> 7 <title>Corepack | Node.js v14.21.2 Documentation</title> 8 <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:400,700,400italic&display=fallback"> 9 <link rel="stylesheet" href="assets/style.css"> 10 <link rel="stylesheet" href="assets/hljs.css"> 11 <link rel="canonical" href="https://nodejs.org/api/corepack.html"> 12</head> 13<body class="alt apidoc" id="api-section-corepack"> 14 <div id="content" class="clearfix"> 15 <div id="column2" class="interior"> 16 <div id="intro" class="interior"> 17 <a href="/" title="Go back to the home page"> 18 Node.js 19 </a> 20 </div> 21 <ul> 22<li><a href="documentation.html" class="nav-documentation">About this documentation</a></li> 23<li><a href="synopsis.html" class="nav-synopsis">Usage and example</a></li> 24</ul> 25<hr class="line"> 26<ul> 27<li><a href="assert.html" class="nav-assert">Assertion testing</a></li> 28<li><a href="async_hooks.html" class="nav-async_hooks">Async hooks</a></li> 29<li><a href="buffer.html" class="nav-buffer">Buffer</a></li> 30<li><a href="addons.html" class="nav-addons">C++ addons</a></li> 31<li><a href="n-api.html" class="nav-n-api">C/C++ addons with Node-API</a></li> 32<li><a href="embedding.html" class="nav-embedding">C++ embedder API</a></li> 33<li><a href="child_process.html" class="nav-child_process">Child processes</a></li> 34<li><a href="cluster.html" class="nav-cluster">Cluster</a></li> 35<li><a href="cli.html" class="nav-cli">Command-line options</a></li> 36<li><a href="console.html" class="nav-console">Console</a></li> 37<li><a href="corepack.html" class="nav-corepack active">Corepack</a></li> 38<li><a href="crypto.html" class="nav-crypto">Crypto</a></li> 39<li><a href="debugger.html" class="nav-debugger">Debugger</a></li> 40<li><a href="deprecations.html" class="nav-deprecations">Deprecated APIs</a></li> 41<li><a href="diagnostics_channel.html" class="nav-diagnostics_channel">Diagnostics Channel</a></li> 42<li><a href="dns.html" class="nav-dns">DNS</a></li> 43<li><a href="domain.html" class="nav-domain">Domain</a></li> 44<li><a href="errors.html" class="nav-errors">Errors</a></li> 45<li><a href="events.html" class="nav-events">Events</a></li> 46<li><a href="fs.html" class="nav-fs">File system</a></li> 47<li><a href="globals.html" class="nav-globals">Globals</a></li> 48<li><a href="http.html" class="nav-http">HTTP</a></li> 49<li><a href="http2.html" class="nav-http2">HTTP/2</a></li> 50<li><a href="https.html" class="nav-https">HTTPS</a></li> 51<li><a href="inspector.html" class="nav-inspector">Inspector</a></li> 52<li><a href="intl.html" class="nav-intl">Internationalization</a></li> 53<li><a href="modules.html" class="nav-modules">Modules: CommonJS modules</a></li> 54<li><a href="esm.html" class="nav-esm">Modules: ECMAScript modules</a></li> 55<li><a href="module.html" class="nav-module">Modules: <code>module</code> API</a></li> 56<li><a href="packages.html" class="nav-packages">Modules: Packages</a></li> 57<li><a href="net.html" class="nav-net">Net</a></li> 58<li><a href="os.html" class="nav-os">OS</a></li> 59<li><a href="path.html" class="nav-path">Path</a></li> 60<li><a href="perf_hooks.html" class="nav-perf_hooks">Performance hooks</a></li> 61<li><a href="policy.html" class="nav-policy">Policies</a></li> 62<li><a href="process.html" class="nav-process">Process</a></li> 63<li><a href="punycode.html" class="nav-punycode">Punycode</a></li> 64<li><a href="querystring.html" class="nav-querystring">Query strings</a></li> 65<li><a href="readline.html" class="nav-readline">Readline</a></li> 66<li><a href="repl.html" class="nav-repl">REPL</a></li> 67<li><a href="report.html" class="nav-report">Report</a></li> 68<li><a href="stream.html" class="nav-stream">Stream</a></li> 69<li><a href="string_decoder.html" class="nav-string_decoder">String decoder</a></li> 70<li><a href="timers.html" class="nav-timers">Timers</a></li> 71<li><a href="tls.html" class="nav-tls">TLS/SSL</a></li> 72<li><a href="tracing.html" class="nav-tracing">Trace events</a></li> 73<li><a href="tty.html" class="nav-tty">TTY</a></li> 74<li><a href="dgram.html" class="nav-dgram">UDP/datagram</a></li> 75<li><a href="url.html" class="nav-url">URL</a></li> 76<li><a href="util.html" class="nav-util">Utilities</a></li> 77<li><a href="v8.html" class="nav-v8">V8</a></li> 78<li><a href="vm.html" class="nav-vm">VM</a></li> 79<li><a href="wasi.html" class="nav-wasi">WASI</a></li> 80<li><a href="worker_threads.html" class="nav-worker_threads">Worker threads</a></li> 81<li><a href="zlib.html" class="nav-zlib">Zlib</a></li> 82</ul> 83<hr class="line"> 84<ul> 85<li><a href="https://github.com/nodejs/node" class="nav-https-github-com-nodejs-node">Code repository and issue tracker</a></li> 86</ul> 87 </div> 88 89 <div id="column1" data-id="corepack" class="interior"> 90 <header> 91 <div class="header-container"> 92 <h1>Node.js v14.21.2 documentation</h1> 93 <button class="theme-toggle-btn" id="theme-toggle-btn" title="Toggle dark mode/light mode" aria-label="Toggle dark mode/light mode" hidden> 94 <svg xmlns="http://www.w3.org/2000/svg" class="icon dark-icon" height="24" width="24"> 95 <path fill="none" d="M0 0h24v24H0z" /> 96 <path d="M11.1 12.08c-2.33-4.51-.5-8.48.53-10.07C6.27 2.2 1.98 6.59 1.98 12c0 .14.02.28.02.42.62-.27 1.29-.42 2-.42 1.66 0 3.18.83 4.1 2.15A4.01 4.01 0 0111 18c0 1.52-.87 2.83-2.12 3.51.98.32 2.03.5 3.11.5 3.5 0 6.58-1.8 8.37-4.52-2.36.23-6.98-.97-9.26-5.41z"/> 97 <path d="M7 16h-.18C6.4 14.84 5.3 14 4 14c-1.66 0-3 1.34-3 3s1.34 3 3 3h3c1.1 0 2-.9 2-2s-.9-2-2-2z"/> 98 </svg> 99 <svg xmlns="http://www.w3.org/2000/svg" class="icon light-icon" height="24" width="24"> 100 <path d="M0 0h24v24H0z" fill="none" /> 101 <path d="M6.76 4.84l-1.8-1.79-1.41 1.41 1.79 1.79 1.42-1.41zM4 10.5H1v2h3v-2zm9-9.95h-2V3.5h2V.55zm7.45 3.91l-1.41-1.41-1.79 1.79 1.41 1.41 1.79-1.79zm-3.21 13.7l1.79 1.8 1.41-1.41-1.8-1.79-1.4 1.4zM20 10.5v2h3v-2h-3zm-8-5c-3.31 0-6 2.69-6 6s2.69 6 6 6 6-2.69 6-6-2.69-6-6-6zm-1 16.95h2V19.5h-2v2.95zm-7.45-3.91l1.41 1.41 1.79-1.8-1.41-1.41-1.79 1.8z"/> 102 </svg> 103 </button> 104 </div> 105 <div id="gtoc"> 106 <ul> 107 <li> 108 <a href="index.html">Index</a> 109 </li> 110 <li> 111 <a href="all.html">View on single page</a> 112 </li> 113 <li> 114 <a href="corepack.json">View as JSON</a> 115 </li> 116 117 <li class="version-picker"> 118 <a href="#">View another version <span>▼</span></a> 119 <ol class="version-picker"><li><a href="https://nodejs.org/docs/latest-v19.x/api/corepack.html">19.x</a></li> 120<li><a href="https://nodejs.org/docs/latest-v18.x/api/corepack.html">18.x <b>LTS</b></a></li> 121<li><a href="https://nodejs.org/docs/latest-v17.x/api/corepack.html">17.x</a></li> 122<li><a href="https://nodejs.org/docs/latest-v16.x/api/corepack.html">16.x <b>LTS</b></a></li> 123<li><a href="https://nodejs.org/docs/latest-v15.x/api/corepack.html">15.x</a></li> 124<li><a href="https://nodejs.org/docs/latest-v14.x/api/corepack.html">14.x <b>LTS</b></a></li></ol> 125 </li> 126 127 <li class="edit_on_github"><a href="https://github.com/nodejs/node/edit/master/doc/api/corepack.md">Edit on GitHub</a></li> 128 </ul> 129 </div> 130 <hr> 131 </header> 132 133 <details id="toc" open><summary>Table of contents</summary><ul> 134<li><span class="stability_1"><a href="#corepack_corepack">Corepack</a></span> 135<ul> 136<li><a href="#corepack_workflows">Workflows</a> 137<ul> 138<li><a href="#corepack_enabling_the_feature">Enabling the feature</a></li> 139<li><a href="#corepack_configuring_a_package">Configuring a package</a></li> 140<li><a href="#corepack_upgrading_the_global_versions">Upgrading the global versions</a></li> 141<li><a href="#corepack_offline_workflow">Offline workflow</a></li> 142</ul> 143</li> 144<li><a href="#corepack_supported_package_managers">Supported package managers</a></li> 145<li><a href="#corepack_common_questions">Common questions</a> 146<ul> 147<li><a href="#corepack_how_does_corepack_currently_interact_with_npm">How does Corepack currently interact with npm?</a></li> 148<li><a href="#corepack_running_npm_install_g_yarn_doesn_t_work">Running <code>npm install -g yarn</code> doesn't work</a></li> 149</ul> 150</li> 151</ul> 152</li> 153</ul></details> 154 155 <div id="apicontent"> 156 <h2>Corepack<span><a class="mark" href="#corepack_corepack" id="corepack_corepack">#</a></span></h2> 157 158 159<p></p><div class="api_stability api_stability_1"><a href="documentation.html#documentation_stability_index">Stability: 1</a> - Experimental</div><p></p> 160<p><em><a href="https://github.com/nodejs/corepack">Corepack</a></em> is an experimental tool to help with 161managing versions of your package managers. It exposes binary proxies for 162each <a href="#corepack_supported_package_managers">supported package manager</a> that, when called, will identify whatever 163package manager is configured for the current project, transparently install 164it if needed, and finally run it without requiring explicit user interactions.</p> 165<p>This feature simplifies two core workflows:</p> 166<ul> 167<li> 168<p>It eases new contributor onboarding, since they won't have to follow 169system-specific installation processes anymore just to have the package 170manager you want them to.</p> 171</li> 172<li> 173<p>It allows you to ensure that everyone in your team will use exactly the 174package manager version you intend them to, without them having to 175manually synchronize it each time you need to make an update.</p> 176</li> 177</ul> 178<section><h3>Workflows<span><a class="mark" href="#corepack_workflows" id="corepack_workflows">#</a></span></h3> 179<h4>Enabling the feature<span><a class="mark" href="#corepack_enabling_the_feature" id="corepack_enabling_the_feature">#</a></span></h4> 180<p>Due to its experimental status, Corepack currently needs to be explicitly 181enabled to have any effect. To do that simply run <a href="https://github.com/nodejs/corepack#corepack-enable--name"><code>corepack enable</code></a>, which 182will set up the symlinks in your environment, next to the <code>node</code> binary 183(and overwrite the existing symlinks if necessary).</p> 184<p>From this point forward, any call to the <a href="#corepack_supported_package_managers">supported binaries</a> will work 185without further setup. Should you experience a problem, just run 186<a href="https://github.com/nodejs/corepack#corepack-disable--name"><code>corepack disable</code></a> to remove the proxies from your system (and consider 187opening up an issue on the <a href="https://github.com/nodejs/corepack">Corepack repository</a> to let us know).</p> 188<h4>Configuring a package<span><a class="mark" href="#corepack_configuring_a_package" id="corepack_configuring_a_package">#</a></span></h4> 189<p>The Corepack proxies will find the closest <a href="packages.html#packages_node_js_package_json_field_definitions"><code>package.json</code></a> file in your 190current directory hierarchy to extract its <a href="packages.html#packages_packagemanager"><code>"packageManager"</code></a> property.</p> 191<p>If the value corresponds to a <a href="#corepack_supported_package_managers">supported package manager</a>, Corepack will make 192sure that all calls to the relevant binaries are run against the requested 193version, downloading it on demand if needed, and aborting if it cannot be 194successfully retrieved.</p> 195<h4>Upgrading the global versions<span><a class="mark" href="#corepack_upgrading_the_global_versions" id="corepack_upgrading_the_global_versions">#</a></span></h4> 196<p>When running outside of an existing project (for example when running 197<code>yarn init</code>), Corepack will by default use predefined versions roughly 198corresponding to the latest stable releases from each tool. Those versions can 199be easily overriden by running the <a href="https://github.com/nodejs/corepack#corepack-prepare--nameversion"><code>corepack prepare</code></a> command along with the 200package manager version you wish to set:</p> 201<pre><code class="language-bash">corepack prepare yarn@x.y.z --activate</code></pre> 202<h4>Offline workflow<span><a class="mark" href="#corepack_offline_workflow" id="corepack_offline_workflow">#</a></span></h4> 203<p>Many production environments don't have network access. Since Corepack 204usually downloads the package manager releases straight from their registries, 205it can conflict with such environments. To avoid that happening, call the 206<a href="https://github.com/nodejs/corepack#corepack-prepare--nameversion"><code>corepack prepare</code></a> command while you still have network access (typically at 207the same time you're preparing your deploy image). This will ensure that the 208required package managers are available even without network access.</p> 209<p>The <code>prepare</code> command has <a href="https://github.com/nodejs/corepack#utility-commands">various flags</a>, consult the detailed 210<a href="https://github.com/nodejs/corepack#readme">Corepack documentation</a> for more information on the matter.</p> 211</section><section><h3>Supported package managers<span><a class="mark" href="#corepack_supported_package_managers" id="corepack_supported_package_managers">#</a></span></h3> 212<p>The following binaries are provided through Corepack:</p> 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230<table><thead><tr><th>Package manager</th><th>Binary names</th></tr></thead><tbody><tr><td><a href="https://yarnpkg.com">Yarn</a></td><td><code>yarn</code>, <code>yarnpkg</code></td></tr><tr><td><a href="https://pnpm.js.org">pnpm</a></td><td><code>pnpm</code>, <code>pnpx</code></td></tr></tbody></table> 231</section><section><h3>Common questions<span><a class="mark" href="#corepack_common_questions" id="corepack_common_questions">#</a></span></h3> 232<h4>How does Corepack currently interact with npm?<span><a class="mark" href="#corepack_how_does_corepack_currently_interact_with_npm" id="corepack_how_does_corepack_currently_interact_with_npm">#</a></span></h4> 233<p>While Corepack could easily support npm like any other package manager, its 234shims aren't currently enabled by default. This has a few consequences:</p> 235<ul> 236<li>It's always possible to run a <code>npm</code> command within a project configured to</li> 237</ul> 238<p>be used with another package manager, since Corepack cannot intercept it.</p> 239<ul> 240<li>While <code>npm</code> is a valid option in the <a href="packages.html#packages_packagemanager"><code>"packageManager"</code></a> property, the</li> 241</ul> 242<p>lack of shim will cause the global npm to be used.</p> 243<h4>Running <code>npm install -g yarn</code> doesn't work<span><a class="mark" href="#corepack_running_npm_install_g_yarn_doesn_t_work" id="corepack_running_npm_install_g_yarn_doesn_t_work">#</a></span></h4> 244<p>npm prevents accidentally overriding the Corepack binaries when doing a global 245install. To avoid this problem, consider one of the following options:</p> 246<ul> 247<li>Don't run this command anymore; Corepack will provide the package manager</li> 248</ul> 249<p>binaries anyway and will ensure that the requested versions are always 250available, so installing the package managers explicitly isn't needed anymore.</p> 251<ul> 252<li>Add the <code>--force</code> flag to <code>npm install</code>; this will tell npm that it's fine to</li> 253</ul> 254<p>override binaries, but you'll erase the Corepack ones in the process (should 255that happen, run <a href="https://github.com/nodejs/corepack#corepack-enable--name"><code>corepack enable</code></a> again to add them back).</p></section> 256 <!-- API END --> 257 </div> 258 </div> 259 </div> 260 <script> 261 'use strict'; 262 { 263 const kCustomPreference = 'customDarkTheme'; 264 const userSettings = sessionStorage.getItem(kCustomPreference); 265 const themeToggleButton = document.getElementById('theme-toggle-btn'); 266 if (userSettings === null && window.matchMedia) { 267 const mq = window.matchMedia('(prefers-color-scheme: dark)'); 268 if ('onchange' in mq) { 269 function mqChangeListener(e) { 270 document.body.classList.toggle('dark-mode', e.matches); 271 } 272 mq.addEventListener('change', mqChangeListener); 273 if (themeToggleButton) { 274 themeToggleButton.addEventListener('click', function() { 275 mq.removeEventListener('change', mqChangeListener); 276 }, { once: true }); 277 } 278 } 279 if (mq.matches) { 280 document.body.classList.add('dark-mode'); 281 } 282 } else if (userSettings === 'true') { 283 document.body.classList.add('dark-mode'); 284 } 285 if (themeToggleButton) { 286 themeToggleButton.hidden = false; 287 themeToggleButton.addEventListener('click', function() { 288 sessionStorage.setItem( 289 kCustomPreference, 290 document.body.classList.toggle('dark-mode') 291 ); 292 }); 293 } 294 } 295 </script> 296</body> 297</html> 298