`yarn run` doesn't work in Git Bash due to strange path modification

[borekb]

Yarn 1.6.0, Git Bash on Windows and this package.json:

{
  "name": "test",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "start": "MSYS_NO_PATHCONV=1 docker run --rm -it -p 8000:8000 -v `pwd`:/docs squidfunk/mkdocs-material:2.6.3"
  }
}

npm start works fine, yarn start displays this error:

$ yarn start
yarn run v1.6.0
$ MSYS_NO_PATHCONV=1 docker run --rm -it -p 8000:8000 -v `pwd`:/docs squidfunk/mkdocs-material:2.6.3
/c/Program Files/git/usr/bin/bash: Files\git\bin\bash.exe: No such file or directory
?[2K?[1G?[31merror?[39m Command failed with exit code 127.
?[2K?[1G?[94minfo?[39m Visit ?[1mhttps://yarnpkg.com/en/docs/cli/run?[22m for documentation about this command.

Node v8.10.0, I'm on Windows 10 Pro.

I think this is a regression and was working fine in Yarn 1.5.x.

[chakrihacker]

/usr/bin/zsh: can't open input file: parcel index.html
error Command failed with exit code 127.

Same problem with ubuntu after upgrading to 1.6.x

[borekb]

The only workaround I found was downgrading to 1.5.1, Yarn was unusable with this bug, unfortunately.

[KatieMFritz]

Same problem here.

.yarnrc:

script-shell "C:\\Program Files\\Git\\bin\\bash.exe"
shell "C:\\Program Files\\Git\\bin\\bash.exe"

Terminal:

/usr/bin/bash: Files\Git\bin\bash.exe: No such file or directory

Tried escaping the space (Program\ Files) and using the shortname (PROGRA~) but neither worked.

Node 9.4.0, Windows 10 Pro

[infogulch]

Also fails using:

script-shell "\"C:\\Program Files\\Git\\bin\\bash.exe\""

With:

Cannot find executable: "C:\Program Files\Git\bin\bash.exe"

Downgrading to 1.5.1...

[borekb]

Just to confirm, the issue is still present in 1.7.0.

[martinmckenna]

Also confirming @KatieMFritz's issue.

After downgrading to yarn 1.5.1 from 1.7.0, the whitespace issue is resolved

[borekb]

FYI, I now run Yarn in Git Bash (actually MSYS2 shell with zsh) via an alias like this:

alias yarn='winpty yarn.cmd'

I believe this is the correct way to run Yarn in Git Bash anyway so this resolves the issue for me.

Unfortunately, Git Bash still cannot be used as a script-shell, see #6086, which is another show-stopper for me. So I'm still on 1.5.1 (it's probably just incidental that both issues started appearing in 1.6.0).

[borekb]

If you need to be on the latest version of Yarn and run it from Git Bash & use Git Bash as the shell-script, this combination should probably work:

• Run Yarn through winpty: alias yarn='winpty yarn.cmd'
• Instead of yarn run script, use npm run script

Hopefully Yarn will be fully compatible with Git Bash soon again.

[KatieMFritz]

Has anyone tried this with Yarn 1.9.2?

[dmclean77]

I just tried with v1.9.4 still doesn't work

[borekb]

A quick update:

1. winpty issue

For the first issue with winpty (path translation), I now use a small wrapper script that is in my PATH before node location, called yarn:

#!/bin/sh

winpty node.exe "C:\\Users\\${USER}\\AppData\\Local\\nvs\\default\\node_modules\\yarn\\bin\\yarn.js" "$@"
ret=$?
exit $ret

I then install Yarn with npm i -g yarn@1.5.1 (or any other version) and it will run through winpty.

2. script-shell issue

The other issue is with Bash / zsh being script-shell after which every yarn run command fails with something like:

zsh: can't open input file: /d

The main issue for this is #6086 and an upstream fix in Node.js has actually been merged a couple of weeks ago: nodejs/node#21943. However, this will be released only in Node 11.0.0 which is scheduled to be out in about a month.

For this issue, the only current solution is to stay at yarn@1.5.1 which for some reason I don't quite understand avoids the Node bug.

[borekb]

Can someone try on Node 11 on Windows? nodejs/node#21943 has supposedly shipped in that version so I'm wondering if the issue is resolved (am not on Windows these days).

[patricksevat]

I just upgraded to Node 11.1.0 and executed $ yarn config set script-shell "C:\\Program Files\\Git\\bin\\bash.exe" and $ yarn config set shell "C:\\Program Files\\Git\\bin\\bash.exe" and was able to properly run a package.json script which executes mkdir -p ./foo/bar which I was not able before