Yarn: Progress bar is printed on new lines in Windows in CMD

[bestander]

Do you want to request a feature or report a bug?
bug

What is the current behavior?

Progressbar is printing every new state in a new line in Windows 10 default CMD

Please mention your node.js, yarn and operating system version.
Node 7.3.0
Windows 10

[bestander]

A possible solution https://github.com/lerna/lerna/pull/92/files thanks to @kentaromiura

[Daniel15]

This was supposed to be fixed by #526 😢 It works for me in both Cmder and cmd.exe?

[bestander]

It actually works fine on my home Windows PC which has a few CMD features enabled: bash for windows, chocolatey and maybe some other developer options.
The PC I tested this on was a bare windows 10 with no additional software installed except for node and yarn 0.19

[simonbuchan]

https://github.com/Microsoft/BashOnWindows/issues/1936 seems to imply the issue is specific to certain fonts, i.e. it's a rendering issue not an process output issue.

[kaiyoma]

I see this issue as well when running yarn install. I'm running git bash (part of Node.js 6.9.1) on Windows 10.

[mrmckeb]

It does look like this is caused by the typeface you use. @kaiyoma - which font are you using here?

[kaiyoma]

11-point Consolas. Pretty popular for programmers. :-)

[mrmckeb]

@kaiyoma, take a look at https://github.com/Microsoft/BashOnWindows/issues/1936. Sadly this isn't going to be fixed any time soon. I'm not sure if it's something the Yarn team could help with by doing something different...

[kaiyoma]

Interesting. Are we sure this is the same issue? I'm using the git bash that comes with the Windows installer of Node.js and I haven't installed the "BashOnWindows" project for running Linux binaries. Are they the same thing?

[simonbuchan]

To my knowledge the issue is due to the new support for ANSI escape codes
added to the windows console since the updates as part of support for WSL,
but are by default enabled. Perhaps yarn's progress renderer started
detecting and using ANSI support? Git bash should still be using a windows
node. You could try fiddling with fonts or sizes or disabling advanced
console features in the console options as a workaround for now?

On Wed, 3 May 2017, 12:14 Kyle Getz, [e-mail] wrote:

Interesting. Are we sure this is the same issue? I'm using the git bash
that comes with the Windows installer of Node.js and I haven't installed
the "BashOnWindows" project for running Linux binaries. Are they the same
thing?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/yarnpkg/yarn/issues/2530#issuecomment-298795992, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABwVo35GKxJUeufqaMBnN-MC2zpugiwbks5r18b0gaJpZM4Lq7yE
.

[kaiyoma]

I've disabled progress bars for now (yarn config set no-progress true). Having a font I like is infinitely more important than progress bars, which I never had anyway when using npm.

[sylvainpolletvillard]

I have a similar problem with Hyper and IntelliJ terminal on Windows. It may be related to a new version of Yarn or a Windows update, I'm not sure. It works correctly on Powershell.

[gluons]

Same problem with Windows 10 Creators Update.

Copy from #3383

• On PowerShell:

  

  

• On CMD:

  

  

[gluons]

Excuse me. Does anyone have an idea to fix this? It's really annoying problem. 😢

[simonbuchan]

Change your console font settings to a known good (Been a while, but Consolas 14pt works I think? Depends on font and size combination), or disable yarn progress bars with yarn config set no-progress until new console rendering arrives - see https://github.com/Microsoft/BashOnWindows/issues/1936

[gluons]

@simonbuchan OK. I'm using Fira Mono font now. I'll try yarn config set no-progress. Thank you. 🙇‍♀️

[BYK]

I'm on Windows and I don't have this problem. That said I'm using Conemu and the latest nightlies of Yarn. Just tried in PowerShell with yarn check and it seems fine.

Anyone can try with the latest nightlies and confirm this still exists?

[sylvainpolletvillard]

The problem is solved for me with yarn 0.27.5 on default Windows CMD

[BYK]

The problem is solved for me with yarn 0.27.5 on default Windows CMD

🎉

[KayLeung]

I still experienced the problem. Windows 10 Pro Insider Build 16281

[BYK]

@KayLeung which version of Yarn?

[KayLeung]

@BYK

yarn check v0.27.5

I tried Powershell / CMD / Conemu

[sylvainpolletvillard]

So after a few tests, it appears it depends on the terminal font. Here is my tests with Consolas 20 on the left, and Meslo LG M on the right:

Yet the result is much better than what I had with yarn 0.23

[KayLeung]

I also tried yarn check v1.0.0, same bug.

@sylvainpolletvillard,
It seems Consolas will help in CMD but some square characters like the GIF above.

Conemu with Consolas (tried diff font-size), same bug.

Just reminded the Bar in Jest is working well. Maybe Yarn could borrow some code from there: https://github.com/facebook/jest/pull/3626

[KayLeung]

I've done some quick testing, it worked: https://github.com/yarnpkg/yarn/pull/4317

[gluons]

0.27.5 is still broken for me.

@BYK Do not close the issue that isn't completely resolved.

This issue should be opened until we get confirmed fix. (Maybe #4317 ?)

[BYK]

@BYK Do not close the issue that isn't completely resolved.

I closed the issue because I think this is a bug in Windows, not Yarn. Sorry for not being clear on that.

[BYK]

Okay, I think we need to specify the output encoding when writing or simply do process.stdout.setDefaultEncoding('utf-8'); when creating the reporter.

@KayLeung would you like to give it a try?

[gluons]

Thank you for reopen.
It will be easy to search when someone face this problem and search with default is:issue is:open. 😄

[swrobel]

FWIW, I have this same issue in Terminal.app on macOS 10.12.6 using Hack 2.020. I've tried several different reasonable font sizes, all with the same result.

[gluons]

Wow! Thank you

[gluons]

It's fixed. 🎉

Grab the artifact from https://ci.appveyor.com/project/kittens/yarn/build/3769/job/3owvdyefkpofp10x/artifacts

[BYK]

This was the same issue with #1222.