'ForceSet': is not a member of 'v8::Object'

[jackieron]

hello
I tried to compile version 0.29.3 with nw-gyp.
Nw - gyp rebuild -- target = 0.29.3 - arch = x64
The following error is prompted.

\src\ffi.cc(101): error C2039: 'ForceSet': is not a member of 'v8::Object' [E:\DemoTest\node_modules\ffi\build\ffi_bi
ndings.vcxproj]
C:\Users\Jackieron.nw-gyp\0.29.3\deps\v8\include\v8.h(3070): note: see declaration of 'v8::Object'
..\src\ffi.cc(104): error C2039: 'ForceSet': is not a member of 'v8::Object' [E:\DemoTest\node_modules\ffi\build\ffi_bi
ndings.vcxproj]
C:\Users\Jackieron.nw-gyp\0.29.3\deps\v8\include\v8.h(3070): note: see declaration of 'v8::Object'
..\src\ffi.cc(113): error C2039: 'ForceSet': is not a member of 'v8::Object' [E:\DemoTest\node_modules\ffi\build\ffi_bi
ndings.vcxproj]
C:\Users\Jackieron.nw-gyp\0.29.3\deps\v8\include\v8.h(3070): note: see declaration of 'v8::Object'
..\src\ffi.cc(114): error C2039: 'ForceSet': is not a member of 'v8::Object' [E:\DemoTest\node_modules\ffi\build\ffi_bi
ndings.vcxproj]
C:\Users\Jackieron.nw-gyp\0.29.3\deps\v8\include\v8.h(3070): note: see declaration of 'v8::Object'
..\src\ffi.cc(115): error C2039: 'ForceSet': is not a member of 'v8::Object' [E:\DemoTest\node_modules\ffi\build\ffi_bi
ndings.vcxproj]
C:\Users\Jackieron.nw-gyp\0.29.3\deps\v8\include\v8.h(3070): note: see declaration of 'v8::Object'
..\src\ffi.cc(116): error C2039: 'ForceSet': is not a member of 'v8::Object' [E:\DemoTest\node_modules\ffi\build\ffi_bi
ndings.vcxproj]
C:\Users\Jackieron.nw-gyp\0.29.3\deps\v8\include\v8.h(3070): note: see declaration of 'v8::Object'
..\src\ffi.cc(122): error C2039: 'ForceSet': is not a member of 'v8::Object' [E:\DemoTest\node_modules\ffi\build\ffi_bi
ndings.vcxproj]

[LockonS]

Same problems with v0.29.4

[matonga]

Hi, this pull request solved the issue for me:

#430

(node-net-keepalive will not install in nodejs v9.9 because of this issue on ffi dependecy, so I had to fork net-keepalive, see matonga/node-net-keepalive@0e6220f)

[TomasHubelbauer]

I've hit the same issue, but in my case I was able to downgrade Node to 8.0.0 (it was for a quick hack, not a production project).

[guixue]

Clone the ffi code to your computer global node_modules path,

cd C:\Users\YOUR-NAME\AppData\Roaming\npm\node_modules
git clone git://github.com/node-ffi/node-ffi.git

npm install -g ffi 

[TurkiWalid]

For me, it was a problem of NodeJS, downgrading from v10 to 8.11.3 fixed my problem

[gwicksted]

@guixue unfortunately master didn't work for me. Had to use npm i node-ffi/node-ffi#169773d otherwise it would not compile (node v10, win 10) due to the same errors listed by the OP. All credit goes to @ibmmqmet and this commit Hopefully node-ffi fixes this soon.

[FelikZ]

same here

[alelom]

Same here with latest Node.js version (10.14.0 LTS). Had to revert to 8.11.3.

[Saiftari]

For me also , it was a problem of NodeJS, downgrading from v10 to 8.11.3 fixed my problem too. Thanks!

[arnaudbud]

This is an electron 3.0, 4.0, and a 5.0 beta blocker for us, so we are stuck with 2.0. @walltex for more details.

[timfish]

@arnaudbud, until the above mentioned PR is merged, you can simply install that specific commit direct from the users github, something like:

npm install --save torycl/node-ffi#a6da649e9036511a817b3557aa9e92e152943839

Unfortunately, if they delete that repo, your build will break. A more reliable alternative is to fork yourself and apply the changes in that PR.

[VijaySutariaJCD]

This is still an issue with NodeJS 12.14.0 version ?

[timfish]

We've migrated over to ffi-napi. It was mostly just the case of swapping out the dependencies for the corresponding napi ones (ie. ref-napi, etc).

Because it uses N-API it has much better compatibility between nodejs versions. We've completed a few Electron upgrades without any breakages whereas previously we would be hunting around for PRs/forks that fixed ffi for that specific node version.