The npm ecosystem uses a library called cmd-shim to emulate symlinks on Windows. It spits out .cmd and .ps1 shims that behave like symlinks, invoking the target executable.
It has a bug with creating a shim that delegates to an executable on a different drive letter. (e.g C: -> D: or vice versa)
The npm ecosystem uses a library called cmd-shim to emulate symlinks on Windows. It spits out .cmd and .ps1 shims that behave like symlinks, invoking the target executable.
It has a bug with creating a shim that delegates to an executable on a different drive letter. (e.g C: -> D: or vice versa)
To support this on our end, we should switch to @zkochan/cmd-shim because they have fixed the bug. https://github.com/pnpm/cmd-shim/issues/17
This issue is awaiting a pull request from the community.