NPM Install Failure

[jameswyse]

I'm getting the following error trying to install via NPM:

npm ERR! `sh "-c" "node build/post-install"` failed with 1

This is for the latest release, 0.8.2 does install fine.

Full output:

npm http GET https://registry.npmjs.org/lodash
npm http 304 https://registry.npmjs.org/lodash

> lodash@0.9.2 install /Users/james/Sites/control/node_modules/lodash
> node build/post-install

There was a problem loading the npm registry.
npm ERR! lodash@0.9.2 install: `node build/post-install`
npm ERR! `sh "-c" "node build/post-install"` failed with 1
npm ERR! 
npm ERR! Failed at the lodash@0.9.2 install script.
npm ERR! This is most likely a problem with the lodash package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node build/post-install
npm ERR! You can get their info via:
npm ERR!     npm owner ls lodash
npm ERR! There is likely additional logging output above.

npm ERR! System Darwin 12.2.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "lodash"
npm ERR! cwd /Users/james/Sites/control
npm ERR! node -v v0.8.2
npm ERR! npm -v 1.1.42
npm ERR! code ELIFECYCLE
npm ERR! stack Error: lodash@0.9.2 install: `node build/post-install`
npm ERR! stack `sh "-c" "node build/post-install"` failed with 1
npm ERR! stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/exec.js:56:20)
npm ERR! stack     at ChildProcess.EventEmitter.emit (events.js:91:17)
npm ERR! stack     at Process._handle.onexit (child_process.js:674:10)
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/james/Sites/control/npm-debug.log
npm ERR! not ok code 0

OS: OS X Mountain Lion
Node: 0.8.2
NPM: 1.1.42

[jameswyse]

This seems to stem from the build script not being able to find uglifyjs or clojure compiler, after noticing these are tarred in the vendor directory I extracted them and now it seems to be working!

[jdalton]

Thanks for the report. Check out #97 and #101

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.