Proposition - Node 12 support

[sosoba]

It's time for Node 12.

[danilohgds]

Node 12 is not in LTS until October 22nd, there are dozen of features and other things that would be just as beneficial if not more.

I'd say let's wait until Node12 has matured a bit, and yes I am excited about the performance changes that it has promised.

[anthony-tuininga]

The work with N-API referenced in issue #1053 will work with Node.js 12 without any changes. Take a look there if you are eager!

[cjbj]

I (currently) have no plans to release node-oracledb 3 binaries for Node 12. Convince me otherwise. Early adopters can build the module binary easily enough, and/or build the dev-4.0 branch.

[cjbj]

Heh, a new NAN would be needed for v3.

[sosoba]

I (currently) have no plans to release node-oracledb 3 binaries for Node 12. Convince me otherwise.

Node 12 has one amazing feature. Error stacktrace containing the trace of asynchronous calls.

[cjbj]

Now would be a good time for you to build the amazing-and-will-be-more-amazing node-oracledb 4 dev code and give us some feedback.

[riyadshauk]

@danilohgds @cjbj What about support for ECMAScript Modules so we can import this library? ...I also ran npm install oracle/node-oracledb#dev-4.0, as @cjbj talked about in the above link.

[dmcghan]

@riyadshauk See this: #501 (comment)

[dmcghan]

@riyadshauk I just ran a test and I was able to get it working. Here are the steps:

1. In your module, use this:

   import oracledb from 'oracledb';

2. Make sure your module file has the extension .mjs.
3. Run your module with the experimental-modules flag:

   node --experimental-modules main.mjs

[cjbj]

Perhaps this should be documented... if someone submits a PR :)