Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yarn outdated output not visible in powershell #4758

Closed
pdeva opened this issue Oct 23, 2017 · 6 comments
Closed

yarn outdated output not visible in powershell #4758

pdeva opened this issue Oct 23, 2017 · 6 comments

Comments

@pdeva
Copy link

pdeva commented Oct 23, 2017

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

Bug

What is the current behavior?

The latest version column is invisible in powershell.

Screenshot 1:
image

Screenshot 2 (with selection):
image

If the current behavior is a bug, please provide the steps to reproduce.

Open Windows Powershell, and type yarn outdated.

What is the expected behavior?

The column should be visible in powershell

Please mention your node.js, yarn and operating system version.

Yarn 1.2.1
Windows 10
Node 6.9.5

@ThisWillDoIt
Copy link

ThisWillDoIt commented Oct 23, 2017

@pdeva Did you by any chance install the Windows Fall Creators Update (1709 / 16299.19) already?

I am pretty sure nothing changed on one of my projects (not the yarn version, not the node version, nor any package.json file) since last week when it still worked perfectly fine. The only relevant thing that changed was the Windows Update that took place.

@pdeva
Copy link
Author

pdeva commented Oct 23, 2017

My version of windows:

Version	10.0.15063 Build 15063

@TimeDropsSB
Copy link

I don't have this issue but I am on Windows 7. Chances are it is a Windows 10 Powershell version issue.

image

@Antaris
Copy link

Antaris commented Nov 2, 2017

@ThisWillDoIt I'm also having issues with yarn since installing 1709. I don't want to hijack this issue, but what issues have you encountered since updating?

@vebaspect
Copy link

vebaspect commented Nov 14, 2017

I have the same problem (only in PowerShell).

Windows: 10.0.15063 Build 15063
Yarn: 1.3.2
Node: 8.9.1

@excelsior97
Copy link
Contributor

I will submit a pull request on this in a few days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants