node-gyp fails with node 8 on travis
See original GitHub issueSee the following build history: https://travis-ci.org/ProjectMirador/mirador/builds
This has been a common problem for our contributors who attempt to clone and run the project with npm install
without explicitly setting the node version, and is also an extremely commonly googled error that never seems to have gone away. Most of the time upgrading above node 6 resolves the issue, but other times it requires deleting binaries. What is the root of this problem and what configuration can I implement that will stop this happening for our contributors (and Travis)?
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (12 by maintainers)
Top Results From Across the Web
TravisCI failing on Node BCrypt with node-gyp errors
The issue here is that bcrypt required the use of a c++ library. Travis does not have this installed. To make it work...
Read more >node-gyp - npm
node -gyp - Node.js native addon build tool. Build Status npm. node-gyp is a cross-platform command-line tool written in Node.js for ...
Read more >Latest Node.js topics - Travis CI Community
Topic Replies Views Activity
Mocha not found! travis‑build 1 1006 December 21, 2021
Node_js lts/* failing on Windows · windows 4 951 December 14, 2021
Issue...
Read more >node-gyp | Yarn - Package Manager
node -gyp - Node.js native addon build tool. Build Status npm. node-gyp is a cross-platform command-line tool written in Node.js for compiling native...
Read more >Building a JavaScript and Node.js project - Travis CI Docs
The .nvmrc file is only read when node_js key in your .travis.yml files does not specify a nodejs version. When the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’ve been requiring that for ages, though (since at least Node 4, I think?)
~For posterity:
node
versions are not ABI backwards compatible so the version ofnan
used is incompatible withnode@8.x
~ For posterity, travis needs to be told explicitly to use GCC 4.8 with the following in the.travis.yml
As per https://docs.travis-ci.com/user/languages/javascript-with-nodejs#Node.js-v4-(or-io.js-v3)-compiler-requirements