Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Fails to prepare plugins with latest node on windows #111

Closed
balupton opened this Issue · 0 comments

1 participant

@balupton
Owner
warning: Failed to load the plugin totaldocuments at C:\projects\test/plugins/t
taldocuments. The error follows
    → [2011-12-13 23:58:21.278] [C:\Users\balupton\AppData\Roaming\npm\node_mod
les\docpad\lib\docpad.coffee] [unknown]
warning: An error occured: Command failed: npm ERR! prefix directory not found
npm ERR! Error: ENOENT, no such file or directory 'C:\projects\test\plugins\tot
ldocuments\~\AppData\Roaming\npm'
npm ERR! Report this *entire* log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>
npm ERR!
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "node" "C:\\Users\\balupton\\AppData\\Roaming\\npm\\node_modul
s\\docpad\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! cwd C:\projects\test\plugins\totaldocuments
npm ERR! node -v v0.6.5
npm ERR! npm -v 1.0.106
npm ERR! path C:\projects\test\plugins\totaldocuments\~\AppData\Roaming\npm
npm ERR! code ENOENT
 Error: Command failed: npm ERR! prefix directory not found
npm ERR! Error: ENOENT, no such file or directory 'C:\projects\test\plugins\tot
ldocuments\~\AppData\Roaming\npm'
npm ERR! Report this *entire* log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>
npm ERR!
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "node" "C:\\Users\\balupton\\AppData\\Roaming\\npm\\node_modul
s\\docpad\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! cwd C:\projects\test\plugins\totaldocuments
npm ERR! node -v v0.6.5
npm ERR! npm -v 1.0.106
npm ERR! path C:\projects\test\plugins\totaldocuments\~\AppData\Roaming\npm
npm ERR! code ENOENT

Appears to be due to balupton/docpad@59926f0 and balupton/docpad@691b32a changes for heroku support. Works fine on OSX.

@balupton balupton closed this issue from a commit
@balupton balupton v2.5.0. Properly fixed #111. Split html2jade out of the jade plugin, …
…and disabled by default. Disabled a few other plugins by default too. Changed haml and npm dep verison numbers to support node 0.4.
4f9194a
@balupton balupton closed this in 4f9194a
@balupton balupton referenced this issue from a commit
@balupton balupton v2.5.0. Properly fixed #111. Split html2jade out of the jade plugin, …
…and disabled by default. Disabled a few other plugins by default too. Changed haml and npm dep verison numbers to support node 0.4.
c343712
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.