outaTiME / grunt-replace

Replace text patterns with applause.
MIT License
411 stars 47 forks source link

install fails on Windows 7 #58

Closed kitsguru closed 10 years ago

kitsguru commented 10 years ago

After a new install of node and npm via the windows msi package I receive errors trying to install grunt-replace.

I am using:

17:09 > node -v
v0.10.32

17:13 > npm --version
1.4.28

17:07 > npm install grunt-replace
|
> cson@1.6.1 preinstall J:\@projects\testing\node_modules\grunt-replace\node_mod
ules\applause\node_modules\cson
> node ./cyclic.js

'node' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! cson@1.6.1 preinstall: `node ./cyclic.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the cson@1.6.1 preinstall script.
npm ERR! This is most likely a problem with the cson package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./cyclic.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls cson
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodej
s\\node_modules\\npm\\bin\\npm-cli.js" "install" "grunt-replace"
npm ERR! cwd J:\@projects\testing
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0
outaTiME commented 10 years ago

mmmmm, something wired here ... try to install the cson dependency alone please ...

npm install cson

i dont like the error 'node' is not recognized as an internal or external command, operable program or batch file.

kitsguru commented 10 years ago

I have filed an issue at bevry/cson Issue #50

as I get the same error installing cson alone. Don't see why node is not recognized either.

bluSCALE4 commented 10 years ago

I also added my error message to kitsguru's issue. I'm not getting the 'node' is not recognized though.

outaTiME commented 10 years ago

oups, @kitsguru something wrong in your classpath ???

@bluSCALE4 you are use the same config from @kitsguru ...

kitsguru commented 10 years ago

when running node from bash, node works fine, when run from cmd prompt, I get node not recognized. trying to find what is different and will let you know what I find.

kitsguru commented 10 years ago

GOT IT Way back when I install NVMW as a node package manager. It used a cmd_auto_run.bat file that set the path variable. This overrode the ENV settings. I commented out the set path in the bat file and all is now OK.

The strange thing is that the values for the PATH were the same.