Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An error occured within the child DocPad instance: spawn C:\Program Files\nodejs ENOENT #991

Closed
jash4 opened this issue Aug 16, 2015 · 2 comments

Comments

@jash4
Copy link

jash4 commented Aug 16, 2015

I'm on windows 7 machine and having similar issue like #944

#944

node -v returns v0.12.7
npm -v returns 2.11.3

docpad -V
v6.78.1 (global installation: C:\Users\x\AppData\Roaming\npm\node_modules\docpad

After having installed docpad globally

info: Installed the skeleton succesfully
notice: Shutting down the global DocPad, and starting up the local

I' am able to execute docpad run successfully and subsequently selecting "No Skeleton Template"

Further running docpad run terminates after giving following error

  An error occured within the child DocPad instance: spawn C:\Program Files\nodejs ENOENT

Instead when I run local docpad package using _npm start_ It is working perfectly.


Even installing docpad plugins gives the same error

docpad install eco

An error occured within the child DocPad instance: spawn C:\Program Files\nodejs ENOENT

tried installing node and docpad several times but the issue still persists

@balupton
Copy link
Member

Strange, will you be around tomorrow? Perhaps I can remote in if you'd like.

Seems like for some reason docpad can't find where your node executable is. For now, try just running docpad with the --global flag, so docpad run --global

@balupton
Copy link
Member

Closing due to age. Ecosystem has likely fixed this. Try again with v6.80 or later.

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

No branches or pull requests

3 participants