-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Upgrade-interactive does not work for Node.js above v10.2.0 #5949
Comments
Me too. It hangs. Can't stop it with Ctrl + C. Node: |
Going to close several other issues as duplicates of this one, since this seems to be the oldest issue that reports this. From what I can tell it's specific to Windows + Node 10. If someone who can consistently reproduce this can help debug, it would be appreciated! |
The best lead on tracking this down seems to be #6198 (comment) |
There is a potential freeze when running interactive upgrades after selecting the options. This boiles down to a problem in the `inquirer` library which is used internally to provide the possible options. Updating `inquirer`to the latest version fixes the problem.
I could track this problem down to an old version of inquirer which is beeing used internally. Sent a PR to update to latest version, which seems to bring no incompatibilities but fixes the problem. |
There is a potential freeze when running interactive upgrades after selecting the options. This boiles down to a problem in the `inquirer` library which is used internally to provide the possible options. Updating `inquirer`to the latest version fixes the problem.
) * Fixes potential freeze on win+node10 interactive upgrades (#5949) There is a potential freeze when running interactive upgrades after selecting the options. This boiles down to a problem in the `inquirer` library which is used internally to provide the possible options. Updating `inquirer`to the latest version fixes the problem. * Update CHANGELOG.md
I know this has been merged, but just confirming that running upgrade-interactive off head works for me now! |
Had the same issue with the latest stable of 1.12.1, works with nightly 1.13.0 version. |
1.12.3 has been released which contains this fix. I think this issue can be closed. Thanks at the wonderful yarn team for bringing this in so super fast! |
@contributors: Close? |
Just want to confirm: I'm on Windows 10. With Node v10.15.3 + Yarn 1.10.1 Thanks! (I think this can be closed) |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
After the packages are selected, the installation hangs in place without further output
If the current behavior is a bug, please provide the steps to reproduce.
I updated my version of Node.js from v10.0.0 to v10.4.0, this behavior started from v10.2.0
Steps:
I select packages for updating, I press enter and all
What is the expected behavior?
Updating packages
Please mention your node.js, yarn and operating system version.
Node.js: v10.4.0
Yarn: 1.7.0
Windows: 10
The text was updated successfully, but these errors were encountered: