Unable to compile for node 10.12.0
See original GitHub issueSeeing a bunch of Nan::
-related warnings, and this error:
.\node_modules\ffi\src\ffi.cc(125): error C2039: 'ForceSet': is not a member of 'v8::Object' [.\node_modules\ffi\build\ffi_bindings.vcxproj]
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Failed to compile on Node 10.0.0 · Issue #1490 - GitHub
nodegit fails to compile on Node 10.0.0 and NPM 5.6.0. Here's a way to reproduce the issue: cd ~ mkdir test_repo cd test_repo...
Read more >Error: npm doesn't work with node v0.10.12 - Stack Overflow
Reinstall your Node.js which will install a compatible and latest version of npm. – esengineer. Jul 19, 2013 at 2:46.
Read more >@pact-foundation/pact-node - npm
The question is this - for your JS code to be able to make a call to another API, is this dependent on...
Read more >Can't update nodejs version on machine executor
I have the following step in my config.yml file. e2e: machine: true working_directory: *workspace_root steps: - checkout - run: name: ...
Read more >Starting out errors (new computer, new installation, node-sass ...
I've just built a brand new computer and I'm getting errors when starting a new Ionic project. What am-I missing? I've installed nodejs, ......
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
See pull request #62 which switches from ffi to ffi-napi to fix this.
For v9 at least you can also use the unreleased master ffi from github, i.e. dependency
"ffi": "node-ffi/node-ffi"
. I can’t remember if this works on v10 or not.well, there is your problem right here.
and how is the system supposed to determine that “that”? Do they need to employ staff for building and running unit tests on everything or maybe create a neural network doing that? It’s the maintainers job to maintain the module and ensure it’s compatibility. The registry only list’s it. Just because npm introduced some flags in package.json’s schema to make life easier for everyone doesn’t mean they become responsible for everything. They are not Aplle.
Anyway, no need to be that defensive. What I meant with my original comment was “if someone can close the issue - he might as well add this line into package.json” (no need for a PR - it’s not a functional code base change). But if there is no one left here to do even that - then the topic is exhausted.