felixrieseberg/npm-windows-upgrade

Exits to command after "Do you want to continue?"

Closed this issue · 5 comments

npm-windows-upgrade version 2.3.0. Have just tested this out on 2 different machines - same result.

Following the instructions perfectly, I get to the step where you run the "npm-windows-upgrade" command:

PS C:\WINDOWS\system32> npm-windows-upgrade
npm-windows-upgrade 2.3.0
? This tool will upgrade npm. Do you want to continue? Yes
PS C:\WINDOWS\system32>

Same happens to me.

Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS C:\Users\James> Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
PS C:\Users\James> npm install --global --production npm-windows-upgrade
C:\Users\James\AppData\Roaming\npm\npm-windows-upgrade -> C:\Users\James\AppData\Roaming\npm\node_modules\npm-windows-up
grade\bin\npm-windows-upgrade
npm-windows-upgrade@2.3.0 C:\Users\James\AppData\Roaming\npm\node_modules\npm-windows-upgrade
├── cli-spinner@0.2.5
├── commander@2.9.0 (graceful-readlink@1.0.1)
├── chalk@1.1.3 (ansi-styles@2.2.1, escape-string-regexp@1.0.5, supports-color@2.0.0, has-ansi@2.0.0, strip-ansi@3.0.1)
├── promise@7.1.1 (asap@2.0.3)
├── prompt@1.0.0 (revalidator@0.1.8, pkginfo@0.4.0, colors@1.1.2, read@1.0.7, winston@2.1.1, utile@0.3.0)
├── inquirer@1.0.2 (ansi-escapes@1.4.0, mute-stream@0.0.6, through@2.3.8, cli-width@2.1.0, strip-ansi@3.0.1, pinkie-prom
ise@2.0.1, figures@1.7.0, run-async@2.2.0, cli-cursor@1.0.2, string-width@1.0.1, rx@4.1.0, lodash@4.12.0)
└── regenerator-runtime-only@0.8.38 (promise@6.1.0, es6-symbol@2.0.1)
PS C:\Users\James> npm-windows-upgrade
npm-windows-upgrade 2.3.0
? This tool will upgrade npm. Do you want to continue? Yes
PS C:\Users\James>

Thanks, something is clearly off - I'm also getting reports via E-Mail. I'll probably have a fix out today.

And fixed! Again, thanks for the reports!

Thanks for the quick fix Felix :D

Of course!