Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Some yarn commands such as yarn --vesrion adds empty space after the result:

This only happens in Git Bash and VSCode Integrated Terminal running Git Bash, it doesn't happen when using yarn.cmd --version and also this doesn't happen in cmd.exe or Hyper running Git Bash, and this only started to happen after updating to Windows 10 build 1809.
If the current behavior is a bug, please provide the steps to reproduce.
Run yarn --version in Git Bash
What is the expected behavior?
Commands show output without adding space after it, like this:

Please mention your node.js, yarn and operating system version.
Node.js: 11.6.0
Yarn: 1.14.0 and also tried it in 1.13.0
OS: Windows 10 build 1809
Git: 2.20.1
seems to be Windows issue https://github.com/Microsoft/vscode/issues/45693#issuecomment-449495252
@imsnif I can confirm output is now working as expected in Windows Version 10.0.18334 Build 18334
issue can be closed
I am still having this problem. It doesnt matter if I use bash or cmd. I am on Windows 10.
I am still having this problem. It doesnt matter if I use bash or cmd. I am on Windows 10.
what Windows build are you on?
I still have this problem (only with Git Bash), I'm on W10 build 17763.437
I am still having this problem. It doesnt matter if I use bash or cmd. I am on Windows 10.
what Windows build are you on?
I am on the build 17763.475
I am still having this problem. It doesnt matter if I use bash or cmd. I am on Windows 10.
what Windows build are you on?
I am on the build 17763.475
works in Windows Version 10.0.18334 Build 18334 last i tried. try upgrading
I was update OS to Windows 10 build 1903 and that thing works great.
Thanks @bj00rn.
@mathewhany Do you still have the same issue because i do (when i run a node command like node index.js) and I can't find a resole to that :(

Yep, never went away
Yep, never went away
This is frustrating, I've tried to reinstall git bash and nothing :(
@dragonSiin @IlCallo what windows build are you on?
@bj00rn Windows 10 64bits x64
Sorry for delay.
Same for me : 17763.678
Sorry for delay.
- Windows 10 Pro 64bit
- Version 1809
- Build 17763.678
Updated W10 version (actually it updated itself, but whatever) and now it's finally back to normal :)
It works now ! thanks a lot !
works!!
Is there a fix for
Windows 10 Home
1809
17763.864
This is the latest build release for home edition
(also running Node, however, that shouldn't matter)
Most helpful comment
Updated W10 version (actually it updated itself, but whatever) and now it's finally back to normal :)