These are chat archives for brunch/brunch

28th
Sep 2015
Mauro Oviedo
@moviedo
Sep 28 2015 15:40
hey guys
or hey people i meant
Elan Shanker
@es128
Sep 28 2015 15:40
hi @moviedo
Mauro Oviedo
@moviedo
Sep 28 2015 15:46
does anyone know anything about ansible?
Elan Shanker
@es128
Sep 28 2015 15:46
I’ve heard of it :)
Mauro Oviedo
@moviedo
Sep 28 2015 15:46
I created an ansible role to install nvm and then install global npm packages
works for installing gulp, grunt-cli, bower, etc
but i get this for brunch
hanged: [default] => (item={'version': '1.4.x', 'pkg': 'bower'})
failed: [default] => (item={'version': '1.8.x', 'pkg': 'brunch'}) => {"cmd": "/home/vagrant/.nvm/versions/node/v0.12.2/bin/npm install --global ''", "failed": true, "item": {"pkg": "brunch", "version": "1.8.x"}, "rc": 1}
stderr: npm WARN optional dep failed, continuing fsevents@0.3.8
sh: 1: node: not found
npm ERR! Linux 3.2.0-90-virtual
npm ERR! argv "/home/vagrant/.nvm/versions/node/v0.12.2/bin/node" "/home/vagrant/.nvm/versions/node/v0.12.2/bin/npm" "install" "--global" "brunch@1.8.x"
npm ERR! node v0.12.2
npm ERR! npm  v2.7.4
npm ERR! code ELIFECYCLE

npm ERR! brunch@1.8.5 postinstall: `node -e "require('fs').readdir('lib',function(e){e&&require('child_process').exec('npm run prepublish')})"`
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the brunch@1.8.5 postinstall script 'node -e "require('fs').readdir('lib',function(e){e&&require('child_process').exec('npm run prepublish')})"'.
npm ERR! This is most likely a problem with the brunch package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node -e "require('fs').readdir('lib',function(e){e&&require('child_process').exec('npm run prepublish')})"
npm ERR! You can get their info via:
npm ERR!     npm owner ls brunch
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/vagrant/npm-debug.log

stdout: /home/vagrant/.nvm/versions/node/v0.12.2/bin/brunch -> /home/vagrant/.nvm/versions/node/v0.12.2/lib/node_modules/brunch/bin/brunch

> brunch@1.8.5 postinstall /home/vagrant/.nvm/versions/node/v0.12.2/lib/node_modules/brunch
> node -e "require('fs').readdir('lib',function(e){e&&require('child_process').exec('npm run prepublish')})"


msg: npm WARN optional dep failed, continuing fsevents@0.3.8
sh:********@1.8.5 postinstall script 'node -e "require('fs').readdir('lib',function(e){e&&require('child_process').exec('npm run prepublish')})"'.
npm ERR! This is most likely a problem with the brunch package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node -e "require('fs').readdir('lib',function(e){e&&require('child_process').exec('npm run prepublish')})"
npm ERR! You can get their info via:
npm ERR!     npm owner ls brunch
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/vagrant/npm-debug.log

FATAL: all hosts have already failed — aborting
Elan Shanker
@es128
Sep 28 2015 15:47
it’s the postinstall script
apparently there’s no node binary available to run commands with in that environment
Try setting it to run node -v after it’s done installing nvm
somehow node isn’t making it into the PATH it seems
Mauro Oviedo
@moviedo
Sep 28 2015 15:50
thanks
i’ll look into this