Comments (24)
s-limo
commented on May 13, 2024
5
Please check if your powershell is in PATH. Solution could be run the following command (or update system PATH variable) before running npm-windows-upgrade
c:> set path=%path%;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\
from npm-windows-upgrade.
tnguven
commented on May 13, 2024
+1
from npm-windows-upgrade.
felixrieseberg
commented on May 13, 2024
Hey, thanks for reporting! I'm wondering if I just introduced a bug - could you do me a favor and try runnig npm install -g [email protected]?
from npm-windows-upgrade.
gregoryagu
commented on May 13, 2024
Ok, so I did npm install of 0.4.4 and ran it, but the error message is exactly the same.
PS C:\Users\Gregg> npm-windows-upgrade
npm-windows-upgrade 0.4.4
? This tool will upgrade npm. Do you want to continue? Yes
events.js:85
throw er; // Unhandled 'error' event
^
Error: spawn powershell.exe ENOENT
at exports._errnoException (util.js:746:11)
at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
at child_process.js:1144:20
at process._tickCallback (node.js:355:11)
from npm-windows-upgrade.
felixrieseberg
commented on May 13, 2024
While I'm sorry that you're still having trouble, I'm happy that we're not looking at a regression. Would you mind telling me your versions of npm and Node - and also how you installed them initially?
from npm-windows-upgrade.
gregoryagu
commented on May 13, 2024
npm: 2.11.3 Installed through the usual installer. Nothing special.
Node: 0.7.12 Also installed through the usual installer. Nothing special.
I tried running it again just to see if it would work, but the result was the same.
from npm-windows-upgrade.
powpow12
commented on May 13, 2024
running into same issue with windows 8.1, also confirmed with version 0.4.4
npm-windows-upgrade error
PS C:\Users\User\Documents\repos\usda> npm-windows-upgrade --npm-path:"C:\Program Files\nodejs"
npm-windows-upgrade 0.4.6
? This tool will upgrade npm. Do you want to continue? (Y/n) Y
? This tool will upgrade npm. Do you want to continue? Yes
events.js:141
throw er; // Unhandled 'error' event
^
Error: spawn powershell.exe ENOENT
at exports._errnoException (util.js:874:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at doNTCallback2 (node.js:439:9)
at process._tickCallback (node.js:353:17)
npm version
PS C:\Users\User\Documents\repos\usda> npm version
{ npm: '3.3.8',
ares: '1.10.1-DEV',
http_parser: '2.5.0',
icu: '56.1',
modules: '46',
node: '4.2.1',
openssl: '1.0.2d',
uv: '1.7.5',
v8: '4.5.103.35',
zlib: '1.2.8' }
from npm-windows-upgrade.
flpms
commented on May 13, 2024
Same problem on Windows 7.
When I run on PowerShell I receive this:
throw er; // Unhandled 'error' event
^
Error: spawn powershell.exe ENOENT
at exports._errnoException (util.js:874:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at doNTCallback2 (node.js:439:9)
at process._tickCallback (node.js:353:17)
And when I run with a MINGW64 receive a different error (I will past all stack to help)
throw err;
^
SyntaxError: Invalid regular expression: /.{1,0}/: numbers out of order in {} quantifier.
at RegExp (native)
at new RegExp (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\babel\node_modules\babel-core\node_modules\core-js\modules\es6.regexp.constructor.js:23:11)
at breakLines (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\inquirer\lib\utils\screen-manager.js:108:15)
at ScreenManager.render (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\inquirer\lib\utils\screen-manager.js:55:22)
at Prompt.render (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\inquirer\lib\prompts\confirm.js:85:15)
at Prompt.onKeypress (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\inquirer\lib\prompts\confirm.js:109:10)
at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\inquirer\node_modules\rx-lite\rx.lite.js:1535:12)
at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\inquirer\node_modules\rx-lite\rx.lite.js:1469:31)
at AnonymousObserver.tryCatcher (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\inquirer\node_modules\rx-lite\rx.lite.js:63:31)
at AutoDetachObserverPrototype.next (C:\Users\myuser\AppData\Roaming\npm\node_modules\npm-windows-upgrade\node_modules\inquirer\node_modules\rx-lite\rx.lite.js:5782:51)
from npm-windows-upgrade.
felixrieseberg
commented on May 13, 2024
Thank you all for your detailed reports. According to the errors, Node has trouble launching PowerShell - which really shouldn't be an issue, which is why I'm having a hard time figuring out what's wrong here.
I released a new version (0.4.7) that sadly won't fix your issue, but it will tell us what is actually wrong by printing the "unhandled error".
I would be extremely thankful if one of you could give it a try - I'd love to fix this issue for all of you and your console output will be key to figuring out what's wrong.
from npm-windows-upgrade.
powpow12
commented on May 13, 2024
here you go
PS C:\Users\User\Documents\repos\ocd-housing-waitlist> npm install -g [email protected]
npm WARN install Couldn't install optional dependency: Unsupported
C:\Program Files\nodejs\npm-windows-upgrade -> C:\Program Files\nodejs\node_modules\npm-windows-upgrade\bin\npm-windows-
upgrade
C:\Program Files\nodejs
└─┬ [email protected]
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├─┬ [email protected]
│ │ │ ├── [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ ├── [email protected]
│ │ │ └── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├─┬ [email protected]
│ │ │ │ │ └─┬ [email protected]
│ │ │ │ │ ├── [email protected]
│ │ │ │ │ └── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ └── [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├─┬ [email protected]
│ │ │ │ │ └── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ └─┬ [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├─┬ [email protected]
│ │ │ │ │ ├─┬ [email protected]
│ │ │ │ │ │ └─┬ [email protected]
│ │ │ │ │ │ ├─┬ [email protected]
│ │ │ │ │ │ │ └── [email protected]
│ │ │ │ │ │ └── [email protected]
│ │ │ │ │ ├── [email protected]
│ │ │ │ │ └── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├─┬ [email protected]
│ │ │ │ │ └─┬ [email protected]
│ │ │ │ │ └── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ └── [email protected]
│ │ │ ├── [email protected]
│ │ │ └─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├─┬ [email protected]
│ │ │ ├── [email protected]
│ │ │ ├── [email protected]
│ │ │ ├── [email protected]
│ │ │ └─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ ├─┬ [email protected]
│ │ │ └─┬ [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ └── [email protected]
│ │ │ ├── [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├─┬ [email protected]
│ │ │ │ │ └─┬ [email protected]
│ │ │ │ │ ├── [email protected]
│ │ │ │ │ ├─┬ [email protected]
│ │ │ │ │ │ └── [email protected]
│ │ │ │ │ └── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ └── [email protected]
│ │ │ ├── [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├─┬ [email protected]
│ │ │ │ │ └── [email protected]
│ │ │ │ └── [email protected]
│ │ │ ├── [email protected]
│ │ │ ├── [email protected]
│ │ │ ├── [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├─┬ [email protected]
│ │ │ │ │ └── [email protected]
│ │ │ │ └── [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ └── [email protected]
│ │ │ └─┬ [email protected]
│ │ │ ├── [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├─┬ [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ └── [email protected]
│ │ │ └── [email protected]
│ │ └─┬ [email protected]
│ │ ├── [email protected]
│ │ └─┬ [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├─┬ [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ └── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └─┬ [email protected]
│ └── [email protected]
└── [email protected]
PS C:\Users\User\Documents\repos\ocd-housing-waitlist> npm version
{ npm: '3.3.8',
ares: '1.10.1-DEV',
http_parser: '2.5.0',
icu: '56.1',
modules: '46',
node: '4.2.1',
openssl: '1.0.2d',
uv: '1.7.5',
v8: '4.5.103.35',
zlib: '1.2.8' }
from npm-windows-upgrade.
gregoryagu
commented on May 13, 2024
PS C:\Users\Gregg> npm-windows-upgrade
npm-windows-upgrade 0.4.7
? This tool will upgrade npm. Do you want to continue? Yes
events.js:85
throw er; // Unhandled 'error' event
^
Error: spawn powershell.exe ENOENT
at exports._errnoException (util.js:746:11)
at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
at child_process.js:1144:20
at process._tickCallback (node.js:355:11)
PS C:\Users\Gregg>
PS C:\Users\Gregg> npm version
{ npm: '2.11.3',
http_parser: '2.3',
modules: '14',
node: '0.12.7',
openssl: '1.0.1p',
uv: '1.6.1',
v8: '3.28.71.19',
zlib: '1.2.8' }
from npm-windows-upgrade.
gregoryagu
commented on May 13, 2024
I don't know if it's any help, but this is the output when installing:
PS C:\Users\Gregg> set-executionPolicy Unrestricted -scope CurrentUser -Force
PS C:\Users\Gregg> npm install -g [email protected]
npm WARN optional dep failed, continuing [email protected]
C:\Users\Gregg\AppData\Roaming\npm\npm-windows-upgrade -> C:\Users\Gregg\AppData\Roaming\npm\node_modules\npm-windows-up
grade\bin\npm-windows-upgrade
npm WARN unmet dependency C:\Users\Gregg\AppData\Roaming\npm\node_modules\you\node_modules\node-sass requires optimist@'
0.6.x' but will load
npm WARN unmet dependency C:\Users\Gregg\AppData\Roaming\npm\node_modules\you\node_modules\optimist,
npm WARN unmet dependency which is version 0.5.0
npm WARN unmet dependency C:\Users\Gregg\AppData\Roaming\npm\node_modules\you\node_modules\express\node_modules\connect
requires cookie@'0.0.5' but will load
npm WARN unmet dependency C:\Users\Gregg\AppData\Roaming\npm\node_modules\you\node_modules\express\node_modules\cookie,
npm WARN unmet dependency which is version 0.1.0
[email protected] C:\Users\Gregg\AppData\Roaming\npm\node_modules\npm-windows-upgrade
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
.8, [email protected], [email protected], [email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], convert-source-map
@1.1.1, [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], babel-cor
from npm-windows-upgrade.
sgutkin
commented on May 13, 2024
On Windows 7 SP1 with Visual Studio 2015. I've tried the same process from both Command Prompt and from Powershell.
PS C:\MyRestEight\src\MyRestEight> npm -v
1.4.9
PS C:\MyRestEight\src\MyRestEight> node -v
v0.10.31
From Powershell, I executed : set-executionPolicy Unrestricted -scope CurrentUser -Force
I installed : npm install -g npm-windows-upgrade
C:\MyRestEight\src\MyRestEight>npm-windows-upgrade
npm-windows-upgrade 1.2.1
? This tool will upgrade npm. Do you want to continue? Yes
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1001:11)
at Process.ChildProcess._handle.onexit (child_process.js:792:34)
C:\MyRestEight\src\MyRestEight>ver
Microsoft Windows [Version 6.1.7601]
Path=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExten
sions\Microsoft\TestWindow;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.7;
C:\Program Files (x86)\MSBuild\14.0\bin;C:\Program Files (x86)\Microsoft Visual
Studio 14.0\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Com
mon7\IDE\Extensions\Microsoft\Web Tools\External;C:\Program Files (x86)\Microsof
t Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\node;C:
\Program Files\Git\cmd;C:\Program Files\Git\bin;C:\Program Files (x86)\Microsoft
Visual Studio 14.0\VC\BIN;C:\Program Files (x86)\Microsoft Visual Studio 14.0\C
ommon7\Tools;C:\windows\Microsoft.NET\Framework\v4.0.30319;C:\Program Files (x86
)\Microsoft Visual Studio 14.0\VC\VCPackages;C:\Program Files (x86)\HTML Help Wo
rkshop;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performanc
e Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x86;C:\Program Files (x86)\M
icrosoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools;C:\Python27;C:\Python27\Scr
ipts;C:\Program Files (x86)\Support Tools;c:\Program Files (x86)\Intel\iCLS Cli
ent;c:\Program Files\Intel\iCLS Client;C:\Users\sgutkin.dnx\runtimes\dnx-clr-
win-x86.1.0.0-rc1-update1\bin;C:\Users\sgutkin.dnx\bin;C:\ProgramData\chocolate
y\bin
from npm-windows-upgrade.
felixrieseberg
commented on May 13, 2024
Hey @sgutkin, I have trouble reproducing your issue (I'm using a blank VM to install your version of Node & npm), and then try to run the upgrade. Works fine for me, so something seems to be unique here - do you remember how you installed Node? I'd love to get to the bottom of this.
from npm-windows-upgrade.
sgutkin
commented on May 13, 2024
I simply used the Visual Studio 2015 installation . I am digging in a
bit to try to find out if there is anything odd on my end too. My node
installation seems to live in a Microsoft proprietary location (see
below). I did see that I seem to have a very new folder called
"nodenpm". I'm not sure if it is correct. I also find a file "npmrc"
in the folder : C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\node\etc. It
had an odd mix of forward & backward slashes with one extra . I changed it
to all forward slashes : "prefix = C:/Program Files (x86)/Microsoft
Visual Studio 14.0/Common7/IDE/Extensions/Microsoft/Web
Tools/External/nodenpm"
Directory of C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External
01/19/2016 10:46 AM
.01/19/2016 10:46 AM ..
11/19/2015 02:35 PM bower
07/28/2015 04:51 PM 64 bower.cmd
12/03/2015 02:46 PM git
07/28/2015 04:51 PM 72 grunt.cmd
11/19/2015 02:35 PM grunt-cli
07/28/2015 04:51 PM 65 jsx.cmd
01/19/2016 10:00 AM node
07/28/2015 04:51 PM 23 node.cmd
01/19/2016 10:19 AM nodenpm
11/19/2015 02:35 PM npm
07/28/2015 04:51 PM 67 npm.cmd
01/19/2016 10:48 AM 1,541 npm-debug.log
11/19/2015 02:37 PM react-server
07/28/2015 04:51 PM 68 react-server.cmd
11/19/2015 02:37 PM react-tools
7 File(s) 1,900 bytes
10 Dir(s) 27,783,499,776 bytes free
On Tue, Jan 19, 2016 at 10:48 AM, Felix Rieseberg [email protected]
wrote:
Hey @sgutkin https://github.com/sgutkin, I have trouble reproducing
your issue (I'm using a blank VM to install your version of Node & npm),
and then try to run the upgrade. Works fine for me, so something seems to
be unique here - do you remember how you installed Node? I'd love to get to
the bottom of this.—
Reply to this email directly or view it on GitHub
#41 (comment)
.
from npm-windows-upgrade.
sgutkin
commented on May 13, 2024
Also:
C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External>npm root -g
yields:
C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web
Tools\External\nodenpm\node_modules
.. and this folder DOES NOT EXIST. I have "nodenpm" but it is empty. I
think my NPM actually lives in
C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\npm\node_modules
On Tue, Jan 19, 2016 at 10:55 AM, Seth Gutkin [email protected]
wrote:
I simply used the Visual Studio 2015 installation . I am digging in a
bit to try to find out if there is anything odd on my end too. My node
installation seems to live in a Microsoft proprietary location (see
below). I did see that I seem to have a very new folder called
"nodenpm". I'm not sure if it is correct. I also find a file "npmrc"
in the folder : C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\node\etc. It
had an odd mix of forward & backward slashes with one extra . I changed it
to all forward slashes : "prefix = C:/Program Files (x86)/Microsoft
Visual Studio 14.0/Common7/IDE/Extensions/Microsoft/Web
Tools/External/nodenpm"Directory of C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External01/19/2016 10:46 AM
.
01/19/2016 10:46 AM ..
11/19/2015 02:35 PM bower
07/28/2015 04:51 PM 64 bower.cmd
12/03/2015 02:46 PM git
07/28/2015 04:51 PM 72 grunt.cmd
11/19/2015 02:35 PM grunt-cli
07/28/2015 04:51 PM 65 jsx.cmd
01/19/2016 10:00 AM node
07/28/2015 04:51 PM 23 node.cmd
01/19/2016 10:19 AM nodenpm
11/19/2015 02:35 PM npm
07/28/2015 04:51 PM 67 npm.cmd
01/19/2016 10:48 AM 1,541 npm-debug.log
11/19/2015 02:37 PM react-server
07/28/2015 04:51 PM 68 react-server.cmd
11/19/2015 02:37 PM react-tools
7 File(s) 1,900 bytes
10 Dir(s) 27,783,499,776 bytes freeOn Tue, Jan 19, 2016 at 10:48 AM, Felix Rieseberg <
[email protected]> wrote:Hey @sgutkin https://github.com/sgutkin, I have trouble reproducing
your issue (I'm using a blank VM to install your version of Node & npm),
and then try to run the upgrade. Works fine for me, so something seems to
be unique here - do you remember how you installed Node? I'd love to get to
the bottom of this.—
Reply to this email directly or view it on GitHub
#41 (comment)
.
from npm-windows-upgrade.
sgutkin
commented on May 13, 2024
MS Visual Studio Professional 2015 14.0.24720.00 Update 1 with "Node.js
Tools" 1.1.31104.02
Microsoft Visual Studio Professional 2015
Version 14.0.24720.00 Update 1
Microsoft .NET Framework
Version 4.6.01055
Installed Version: Professional
Visual Basic 2015 00325-60003-25155-AA417
Microsoft Visual Basic 2015
Visual C# 2015 00325-60003-25155-AA417
Microsoft Visual C# 2015
Visual C++ 2015 00325-60003-25155-AA417
Microsoft Visual C++ 2015
Application Insights Tools for Visual Studio Package 1.0
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2015 (RC1 Update 1) 14.1.11120.0
ASP.NET and Web Tools 2015 (RC1 Update 1)
ASP.NET Web Frameworks and Tools 2012.2 4.1.41102.0
For additional information, visit
http://go.microsoft.com/fwlink/?LinkID=309563
ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
For additional information, visit http://www.asp.net/
Azure App Service Tools v2.7.1 14.0.11112.0
Azure App Service Tools v2.7.1
Common Azure Tools 1.6
Provides common services for use by Azure Mobile Services and Microsoft
Azure Tools.
GitHub.VisualStudio 1.0
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.
JetBrains ReSharper Ultimate 2015.2 Build 103.0.20150818.200216
JetBrains ReSharper Ultimate package for Microsoft Visual Studio. For more
information about ReSharper Ultimate, visit
http://www.jetbrains.com/resharper. Copyright © 2016 JetBrains, Inc.
Microsoft Azure HDInsight HQL Service 2.0.2600.0
Language service for Hive query
Microsoft Azure HDInsight Tools for Visual Studio 2.0.2600.0
An integrated development environment for HDInsight application development.
Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools
Microsoft Azure Tools 2.7
Microsoft Azure Tools for Microsoft Visual Studio 2015 - v2.7.30818.1601
Node.js Tools 1.1.31104.02
Adds support for developing and debugging Node.js apps in Visual Studio
Node.js Tools - Profiling 1.1.31104.02
Profiling support for Node.js projects.
NuGet Package Manager 3.3.0
NuGet Package Manager in Visual Studio. For more information about NuGet,
visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from
the PreEmptive Analytics product.
SQL Server Data Tools 14.0.50730.0
Microsoft SQL Server Data Tools
TypeScript 1.7.6.0
TypeScript for Microsoft Visual Studio
Web Essentials 2015 1.0.203
Adds many useful features to Visual Studio for web developers.
On Tue, Jan 19, 2016 at 10:59 AM, Seth Gutkin [email protected]
wrote:
Also:
C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External>npm root -gyields:
C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web
Tools\External\nodenpm\node_modules.. and this folder DOES NOT EXIST. I have "nodenpm" but it is empty.
I think my NPM actually lives inC:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\npm\node_modulesOn Tue, Jan 19, 2016 at 10:55 AM, Seth Gutkin [email protected]
wrote:I simply used the Visual Studio 2015 installation . I am digging in a
bit to try to find out if there is anything odd on my end too. My node
installation seems to live in a Microsoft proprietary location (see
below). I did see that I seem to have a very new folder called
"nodenpm". I'm not sure if it is correct. I also find a file "npmrc"
in the folder : C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\node\etc. It
had an odd mix of forward & backward slashes with one extra . I changed it
to all forward slashes : "prefix = C:/Program Files (x86)/Microsoft
Visual Studio 14.0/Common7/IDE/Extensions/Microsoft/Web
Tools/External/nodenpm"Directory of C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External01/19/2016 10:46 AM
.
01/19/2016 10:46 AM ..
11/19/2015 02:35 PM bower
07/28/2015 04:51 PM 64 bower.cmd
12/03/2015 02:46 PM git
07/28/2015 04:51 PM 72 grunt.cmd
11/19/2015 02:35 PM grunt-cli
07/28/2015 04:51 PM 65 jsx.cmd
01/19/2016 10:00 AM node
07/28/2015 04:51 PM 23 node.cmd
01/19/2016 10:19 AM nodenpm
11/19/2015 02:35 PM npm
07/28/2015 04:51 PM 67 npm.cmd
01/19/2016 10:48 AM 1,541 npm-debug.log
11/19/2015 02:37 PM react-server
07/28/2015 04:51 PM 68 react-server.cmd
11/19/2015 02:37 PM react-tools
7 File(s) 1,900 bytes
10 Dir(s) 27,783,499,776 bytes freeOn Tue, Jan 19, 2016 at 10:48 AM, Felix Rieseberg <
[email protected]> wrote:Hey @sgutkin https://github.com/sgutkin, I have trouble reproducing
your issue (I'm using a blank VM to install your version of Node & npm),
and then try to run the upgrade. Works fine for me, so something seems to
be unique here - do you remember how you installed Node? I'd love to get to
the bottom of this.—
Reply to this email directly or view it on GitHub
#41 (comment)
.
from npm-windows-upgrade.
felixrieseberg
commented on May 13, 2024
Interesting, thanks for the info. It's very possible that Visual Studio installs/installed Node incorrectly - I'll try to spin up a VM with VS and Node to test this out. Thanks for reporting!
from npm-windows-upgrade.
shanehoban
commented on May 13, 2024
While not a solution, this is at least a workaround that worked for me. When trying npm-windows-upgrade on it's own was throwing that error, I tried npm-windows-upgrade -p to skip the initial prompt, which showed me versions but then threw an error.
From there I did npm-windows-upgrade -p --version 3.8.1 and voila, it worked.
I picked the most recent version that displayed when doing the first -p command.
from npm-windows-upgrade.
gurungbinod
commented on May 13, 2024
Thanks @s-limo . It worked with ease!!
from npm-windows-upgrade.
gangadharjannu
commented on May 13, 2024
Thanks @s-limo. It is working!
from npm-windows-upgrade.
MahmoudMabrok
commented on May 13, 2024
u can check this also
#150 (comment)
from npm-windows-upgrade.
v2nagaraj
commented on May 13, 2024
Please check if your powershell is in PATH. Solution could be run the following command (or update system PATH variable) before running npm-windows-upgrade
c:> set path=%path%;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\
from npm-windows-upgrade.
v2nagaraj
commented on May 13, 2024
excellect its worked for me like jump...
from npm-windows-upgrade.
Related Issues (20)
- Scope specified more than once (powershell)
- Error: spawn powershell.exe ENOENT HOT 4
- I got this error at the time of run command "ng serve --open". HOT 1
- expo start not opening project
- npm install
- Can't update problem (even for admin) HOT 2
- npm ERR! cb.apply is not a function While trying to Update the Npm the Windows way. HOT 1
- Failed to upgrade from 6.14.6 to 6.14.8 HOT 2
- Error: Npm start
- Error to upgrade: from 6.14.8 to the latest
- npx create-react-app => Error EINTEGRITY
- Cannot find module 'npm-windows-upgrade.js'
- You wanted to install npm 7.6.1, but the installed version is 6.14.11. HOT 2
- "Scripts cannot be executed on this system." on pwsh 7 if process scope is not Unrestricted
- npm install express --save Error
- npm ERR! code EINTEGRITY
- failed to upgrade npm
- while enter npm start for runt a react app it shows error like this
- Cannot install latest version on Windows HOT 1
- Can't execute npm-windows_update
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from npm-windows-upgrade.