Closed Kekec852 closed 10 years ago
I fixed that a month ago in #27 - get version 2.20 or greater.
I'm using 2.20 and i have this problem.
Maybe there is a problem in version of windows that i use. I'm on Windows Server 2012 R2. NPM version 1.4.14.
Is there any output? Anything logged?
Does it succeed in running npm, and then that fails, or it cannot find npm at all?
There was but than i fix(just changed executable name) it and compile my own version.
But it was about npm is not a valid win32 application. And if i went to npm installation folder npm without any extension exist, but is a bash or sh script. I think there is the root of the problem.
I fixed it to look also for npm.cmd
in 2.21, so that should be dealt with now.
When you change package.json with new lib and you then run project it will ask to run npm install this action will fail on windows because you have npm and npm.cmd in nodejs folder and npm is not valid script/program in windows.
For now i just change NPM_EXECUTABLE in Npm.java to npm.cmd and now is working.