search

CleverStack / cleverstack-cli

CLI for CleverStack
http://youtube.com/watch?v=-4ArURHExhQ
MIT License
196 stars 33 forks source link

init command failed on windows 7 pro 64 bits. #3

Closed rosemaryy closed 10 years ago

rosemaryy commented 10 years ago

My node is v0.10.22 My npm is v1.3.14

npm install -g cleverstack-cli

command executed successfully.

However when I ran

clever init my-app

I got this error.

events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:980:11)
at Process.ChildProcess._handle.onexit (child_process.js:771:34)
rvillars commented 10 years ago

Yep, got the same error.

akamarvin commented 10 years ago

same here

windows 8.1 pro 64bit

my node is 0.10.28 npm is 1.4.9 npm, bower and grunt are in the PATH ( ... C:\Program Files\nodejs\;C:\Users[myuser]\AppData\Roaming\npm ... ) i've got a python 2.7 and a git 1.9.2 , in the PATH also

any clever [something] command won't work (clever init, clever list, even clever help, .... ):

events.js:72
    throw er; // Unhandled 'error' event
          ^ 
Error: spawn ENOENT
at errnoException (child_process.js:998:11)
at Process.ChildProcess._handle.onexit (child_process.js:789:34)

I'm guessing it's still a path or env.var issue for Node, but what ?

when I'm in C:\Users[myuser]\AppData\Roaming\npm\node_modules\cleverstack-cli\bin\ i can try a "node clever-init my-app" , it would start, bu then fails at 20% with the same error.

Creating my-app folder in C:\Users\[myuser]\AppData\Roaming\npm\node_modules\cleve
rstack-cli\bin...
Setting up backend seed...
Setting up frontend seed...
Writing local config file...
Installing NPM packages for C:\Users\[myuser]\AppData\Roaming\npm\node_modules\cle
verstack-cli\bin\my-app\backend
Status @ 1s |   CleverStack Installation: [▒▒--------]  20 %   ┊

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:998:11)
    at Process.ChildProcess._handle.onexit (child_process.js:789:34)

I hope you can reproduce and find out.

pilsy commented 10 years ago

I have discovered that this is caused by this bug in nodejs, https://github.com/joyent/node/issues/2318#issuecomment-3219836

I am working on a fix and should have it completed, tested and ready today - failing that within the next couple of days if i find more issues

pilsy commented 10 years ago

I have been able to reproduce this issue on windows 8 and windows 7 on fresh installs, i have fixed the issue in PR #7 that i just merged.