Node-gyp failures in sfacts/lowdown dependency in Node 4+
See original GitHub issuePosted this to sfacts repo but there doesn’t seem to be much activity over there.
Installing on Mac OS 10.11 with Node 4.1.2 and npm 2.14.4 fails due to an outdated dependency (leveldown) in sfacts. This, in turn, is referencing an old node-gyp, which does not work with node 4.1.2. (Or at least my 4.1.2).
The leveldown dependency in sfacts is at ^0.10.2, meaning it will install 0.10.5. The latest leveldown is 1.4.2. The latest works fine for me, as does latest node-gyp.
Is anyone else experiencing this problem?
Sorry for the cross-posting, but didn’t seem like the other issue was going to be addressed via the sfacts repo.
...
../node_modules/nan/nan.h:1514:12: note: in instantiation of function template specialization 'v8::Local<v8::Function>::Local<v8::Value>' requested here
return NanEscapeScope(NanNew(handle)->Get(kCallbackIndex)
^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
^
In file included from ../src/batch.cc:1:
In file included from /Users/me/.node-gyp/4.1.2/include/node/node.h:42:
/Users/me/.node-gyp/4.1.2/include/node/v8.h:221:5: error: assigning to 'v8::Object *volatile' from incompatible type 'v8::Value *'
TYPE_CHECK(T, S);
^~~~~~~~~~~~~~~~
/Users/me/.node-gyp/4.1.2/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
*(static_cast<T* volatile*>(0)) = static_cast<S*>(0); \
^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:1632:12: note: in instantiation of function template specialization 'v8::Local<v8::Object>::Local<v8::Value>' requested here
return NanEscapeScope(handle->Get(NanNew(key)).As<v8::Object>());
^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
^
9 errors generated.
...
npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/Cellar/nvm/0.25.4/versions/node/v4.1.2/bin/node" "/usr/local/opt/nvm/versions/node/v4.1.2/bin/npm" "i" "sfacts" "--save"
npm ERR! node v4.1.2
npm ERR! npm v2.14.4
npm ERR! code ELIFECYCLE
npm ERR! leveldown@0.10.5 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the leveldown@0.10.5 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the leveldown package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls leveldown
npm ERR! There is likely additional logging output above.
Issue Analytics
- State:
- Created 8 years ago
- Comments:5
Top Results From Across the Web
Solving common issues with node-gyp - LogRocket Blog
Many node-gyp issues are actually issues with the toolchain used for building add-on code. We'll categorize these issues to offer solutions.
Read more >node-gyp keeps failing unreliably on github windows ci. #2683
So I tried isolating dependencies to see how the failures happen in https://github.com/nodech/ci-test. Dependencies used for testing (all three ...
Read more >NPM install fails with node-gyp - Stack Overflow
I tried several days for this build issue, on my PC with Visual Studio 2010 / 2013 / 2015 installed, with no success....
Read more >A Comprehensive Guide to Fixing Node-Gyp Issues on Windows
This guide is meant to help solve the issues that can arise when installing a package that requires node-gyp . 1. Try running...
Read more >Npm install command failing with message "could not find ...
When I run the npm install command, npm starts downloading the dependencies. But then, suddenly, it stops with the error:
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 FreeTop 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
Top GitHub Comments
I am working on Node5 support and I did get it working… but it is not public yet. SuperScript works today on node 0.12.x with no issues.
Travis is telling me that we’re good in the latest Node 4.x, 5.x and 6.x, so hopefully this is not an issue anymore (or at least for v1)!