Closed vdumont closed 7 years ago
cc @dane @springmeyer @bhousel
gyp ERR! node -v v0.10.32
This is a pretty old version of node, and many of your npm dependencies are issuing warnings that they are expecting >4 or so, so I'm not really surprised there are issues with the install. Can you upgrade to a node 4.x or 6.x and try again?
@bhousel Thanks, I can look into updating node but doubt this is the issue here since we've been using this pinned version for over a year (it gives warnings but installs/runs fine). I'm more concerned that it's now complaining about the missing mapnik binaries from the s3 bucket, are you aware of a cleanup that happened on that bucket? EDIT: actually I can curl https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.5.13/Release/node-v11-linux-x64.tar.gz just fine, which makes the error confusing O_o
This is due to request/request#2772. That request release broke node v0.10.x support. Request is used inside node-pre-gyp for downloading the binaries. It is failing - your log shows the problem:
/var/lib/jenkins/workspace/myjob/jenkins-myjob-118-node/lib/node_modules/spritezero-cli/node_modules/spritezero/node_modules/mapnik/node_modules/node-pre-gyp/node_modules/request/node_modules/hawk/node_modules/boom/lib/index.js:5 const Hoek = require('hoek'); ^^^^^
The node-mapnik version you are pulling in uses preinstall
to pull the copy of node-pre-gyp. That means that request is auto-upgraded. You can try using node-mapnik >= 3.6.0 which moved to bundling node-pre-gyp (https://github.com/mapnik/node-mapnik/blob/master/CHANGELOG.md#360) and therefore the request version should not be auto-upgraded.
This impacts all users of any applications using node-pre-gyp and node v0.10.x so I'm working on trying to adapt over at https://github.com/mapbox/node-pre-gyp/pull/319
Because node v0.10.x is deprecated, I'll echo that users hitting this should ideally upgrade to a more recent node version. Also, because this is unrelated to spritezero, I'll close now.
Hi, we are using spritezero-cli@1.1.2 and can't seem install it anymore since it cannot find the mapnik 3.5.13 node module from Mapbox's S3 bucket. (We're still on 1.1.2 since later versions require GCC 5.x). Does this ring a bell?