Fails on Windows + Git BASH

The path to corepack binaries for package managers fail in an emulated Linux environment on Windows.

Below, you can see that it's using both the Windows physical "C:" drive path as well as the emulated Linux "/c/" path. The actual Windows path is: "C:\Program Files\nodejs\node_modules\corepack\dist\yarn.js" and the emulated Linux path is: "/c/Program\ Files/nodejs/node_modules/corepack/dist/yarn.js".

Git for Windows is a popular choice among developers and the Git BASH shell is often the default terminal for many VS Code developers.

It's not currently possible to use corepack in Git BASH and the error doesn't make it obvious what a developer should do unless they happen to know about the underlying pathing.

$ yarn --version
node:internal/modules/cjs/loader:1080
  throw err;
  ^

Error: Cannot find module 'C:\c\Program Files\nodejs\node_modules\corepack\dist\yarn.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
    at Module._load (node:internal/modules/cjs/loader:922:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.18.2

Start by reproducing yarn --version in Git Bash on Windows and trace how Corepack constructs the package-manager binary path. Done means the generated path uses a valid Windows or Git Bash form and the command runs without the MODULE_NOT_FOUND error.