Project abandoned?

[loukamb]

The original library was abandoned. Then, this ABI-stable port got abandoned too? No updates for close to a year now, despite things slowly breaking over time. It is fundamentally compatible with some of the latest versions of Electron.

Should we yet again make another fork that unborks whatever is currently borked?

[alon42]

unfortunately, it seems like an abandoned lib.
if you (or anyone) find any good alternative it will be great to hear

[xan105]

Can't recommend Koffi enough. Give it a try.

[somanuell]

koffi works great, and, added bonus, the author is reactive and helpful!

[LucasBonafe]

Can't recommend Koffi enough. Give it a try.

What about ffi-napi?

[somanuell]

Can't recommend Koffi enough. Give it a try.

What about ffi-napi?

ffi-napi is the name of the npm package on npmjs.com. You are here on github, commenting in an issue for the source repository for that package....

[ikb42]

Does anyone know if any of the forks of this repo address the Node 18 issues?

[cclauss]

• AppVeyor nodejs_version: 16, 18, 20 #255

[Pomax]

Note that even if it's abandoned, ffi-napi seems to still work just fine with Node 20, provided that your Node and library architectures agree (e.g. x86 Node versions won't load arm libraries, and vice versa).

That said, in terms of an active project, koffi is definitely the way to go.

[cclauss]

@Pomax Can we make #255 pass all tests?

[Pomax]

You'll probably want to check which actual versions of Node 18 and 20 get used, and check whether the library you're generating is compatible with that (in terms of platform/architecture). I don't see any actual error traces noted in that PR, so it's pretty hard to tell what's actually going wrong.