Issue when installing docpad 6.53.0 from git bash on Windows #656

Closed
ThorbenLindhauer opened this Issue Sep 24, 2013 · 4 comments

3 participants

@ThorbenLindhauer

Hi,

I have been experiencing issues with installing docpad on my windows machine from git bash.

docpad version: 6.53.0
npm version: 1.3.8
node version: v0.10.18
OS: Windows 7 64 bit

The final part of npm-debug.log is as follows:

1650 error Error: spawn ENOENT
1650 error     at errnoException (child_process.js:980:11)
1650 error     at Process.ChildProcess._handle.onexit (child_process.js:771:34)
1651 error If you need help, you may report this log at:
1651 error     <http://github.com/isaacs/npm/issues>
1651 error or email it to:
1651 error     <npm-@googlegroups.com>
1652 error System Windows_NT 6.1.7601
1653 error command "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
1654 error cwd c:\Thorben\camunda\dev\repos\docs.camunda.org\site
1655 error node -v v0.10.18
1656 error npm -v 1.3.8
1657 error syscall spawn
1658 error code ENOENT
1659 error errno ENOENT
1660 verbose exit [ 1, true ]

while the root cause seems to be located in several modules: taskgroup, ambi, safefs, typechecker. See below:

> taskgroup@3.2.3 preinstall c:\Thorben\camunda\dev\repos\docs.camunda.org\site\
node_modules\docpad-plugin-text\node_modules\bal-util\node_modules\safefs\node_m
odules\taskgroup
> node ./cyclic.js

npm ERR! Error: spawn ENOENT
npm ERR!     at errnoException (child_process.js:980:11)
npm ERR!     at Process.ChildProcess._handle.onexit (child_process.js:771:34)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

In all these scripts, an npm process is spawned. It appears to me that I am seeing this issue: http://stackoverflow.com/questions/17516772/using-nodejss-spawn-causes-unknown-option-and-error-spawn-enoent-err

I found a potential fix in another project, but I am absolutely not familiar with node.js development: gmanolache/express-train@5e21a00

Interestingly I only see the issue when running npm install from git bash. If I use a standard Windows command line, it succeeds, so it is not a blocker for me.

Cheers,
Thorben

@balupton
DocPad member

That's strange, as cyclic should not fire the spawn inside of it... Can you add me on skype (username balupton) or google hangouts (balupton@gmail.com) and I can remote in sometime and debug?

@pflannery

Not sure if you guys managed to fix this but just so your aware..

There is a difference in how the paths work for the different prompts\terminals we use on windows

bash and standard windows prompt use the same path but nodejs cmd prompt isn't quite the same as it uses a batch file to launch the a prompt.

What I find is that when I'm using nodejs prompt and installing global plugins via npm it installs the plugins in to

c:\program files (x86)\nodejs\npm\....

but when in standard prompt or bash it installs global plugins in to

c:\users\{username}\appdata\roaming\npm\....

So probably like me, many windows users will vary between these different prompts during the day without realising and end up installing global npm plugins in different places.

I've had issues in the past where docpad says its not installed when doing a docpad uninstall and yet it runs just fine lol

The work around I found for this is to ensure the path is the same for all prompts by adding the following to the path in the environment variables section in windows

C:\Users\{username}\AppData\Roaming\npm
C:\Users\{username}\AppData\Roaming\npm\node_modules

Hopefully this will fix your ENOENT issue

@balupton
DocPad member

Can you run npm cache clean; npm install -g npm; npm install -g docpad@6.54 and let me know if it still breaks? I've done a bunch of updates.

@balupton balupton closed this Nov 28, 2013
@balupton
DocPad member

Closed due to age.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment