arun@arun-ghoomakad:~/Documents/Work/mapbox/report-dt/get_data$ cd ../get_data && npm install
npm WARN package.json daily-report-data-team@0.0.1 No description
npm WARN package.json daily-report-data-team@0.0.1 No README data
\
> zlib@1.0.5 preinstall /home/arun/Documents/Work/mapbox/report-dt/get_data/node_modules/zlib
> node-waf clean || true; node-waf configure build
sh: 1: node-waf: not found
sh: 1: node-waf: not found
npm ERR! zlib@1.0.5 preinstall: `node-waf clean || true; node-waf configure build`
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the zlib@1.0.5 preinstall script.
npm ERR! This is most likely a problem with the zlib package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf clean || true; node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls zlib
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.13.0-45-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /home/arun/Documents/Work/mapbox/report-dt/get_data
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0
From stackoverflow, node has inbuilt support for zlib.
Everything still seems to work, but we can probably remove zlib from package.json.
nice catch. I'm familiar with that old zlib dep enough to know its not correct to depend on it (like you note) so i've removed. Install should work better now.
From stackoverflow, node has inbuilt support for zlib.
Everything still seems to work, but we can probably remove zlib from package.json.