Switch from robotjs to libnut

[s1hofmann]

Short overview
Currently nut.js uses octalmage/robotjs, a nan module. For easier support of multiple node versions, our N-API port should be elaborated.

Use case
Easier support for multiple node modules without recompiling the native module.

Detailed description

N-API is an ABI stable C interface provided by Node.js for building native addons. It is independent from the underlying JavaScript runtime (e.g. V8 or ChakraCore) and is maintained as part of Node.js itself. It is intended to insulate native addons from changes in the underlying JavaScript engine and allow modules compiled for one version to run on later versions of Node.js without recompilation.

In @nut-tree/libnut, octalmage/robotjs has been ported to N-API, which allows to use it with any node version >= 10 without having to recompile the native module.

[AdrianoFerrari]

Happy to have found nut.js. Any updates on when this will be merged?
Issues with the robotjs package is the main reason I started looking for alternatives...

[s1hofmann]

Hi @AdrianoFerrari,

with the new LTS version of node (lts/erbium), I'm about to release a new version of nut.js quite soon (next week-ish). I'm just currently finishing up on some other tasks.

For now @nut-tree/libnut is basically an N-API port of robotjs with minor changes from my side. May I ask which issues have you been dealing with?

[s1hofmann]

@AdrianoFerrari I published nut.js v1.3.1 today which closes this issue.

[AdrianoFerrari]

Thanks, seems to install properly now on Travis for macOS and linux. Sorry I can't pinpoint what the issue was with robotjs vs libnut. Quick reading shows me that it's possible that robotjs was expecting an older JS engine (I remember the errors having something to do with "V8")...

Anyway, installs now 👍

(still having issues getting it to send keyboard commands on macOS on Travis, but that's very likely something I'm doing wrong... will keep at it).