Migrating NAN to N-API

[mznet]

Expected Behavior

• don't need to recompile robotjs for every nodejs version update

Current Behavior

• need to recompile robotjs and handle something to correspond to nodejs update

Possible Solution

• migrate NAN from N-API

Steps to Reproduce (for bugs)

1. on nodejs version over 10.x, install robotjs using npm
2. while compiling robotjs on machine, compile error will be caused because of NODE_MODULE_VERSION

Context

I found out N-API provides better stability guarantee than NAN while waiting for robotjs 0.6.0. My development envrionment is on node 10.16.1, robotjs caused compile errors or NODE_MODULE_VERSION errors so that I failed to install it. And I realized that many user was struggling for installing robotjs on over node 10.x environment like me.

N-API would be a choice to resolve nodejs version dependency and installation failure.

https://medium.com/the-node-js-collection/n-api-next-generation-node-js-apis-for-native-modules-169af5235b06

Your Environment

• RobotJS version: 0.5.1
• Node.js version: 10.16.1
• npm version: 6.10.2
• Operating System: 10.14.6

[s1hofmann]

Since development seems to stall here I created my own N-API port of RobotJS for use with https://github.com/nut-tree/nut.js.