Migrate to ES modules about alpaca-trade-api-js

[neeschit]

@shlomikushchi - curious on your thoughts on this.

[shlomiku]

let's talk. can you contact me on the alpaca slack channels?

[anonrose]

Hi, is this moving forward? If not I'll be forking and implementing myself.

[neeschit]

btw have you seen this?

https://github.com/117/alpaca

[anonrose]

@neeschit I haven't, I'm going to move forward with that. Thank you!

[neeschit]

Out of curiosity, what versions of Node does this library support? @shlomikushchi

[neeschit]

let's talk. can you contact me on the alpaca slack channels?

To summarize what we spoke offline, maintaining backwards compatibility takes priority over migrating to ESM. We will need to publish a hybrid npm package.

The approach I was looking to use is somewhat detailed here:

https://2ality.com/2019/10/hybrid-npm-packages.html#option-2%3A-bare-import-commonjs%2C-deep-import-esm-(maximum-backward-compatibility)

I will try to create a PR when I have time

[shlomiku]

@neeschit I am unaware of any limitations right now, but if you are - let me know so we could document it.

[neeschit]

Ok, it would be great if we could limit support to Node 12+ or even better, Node 14+ which is now LTS/Default recommended on https://nodejs.org/en/.

If we are comfortable doing that @shlomikushchi, I can cut a PR to migrate to ES modules, building on the work by @anonrose to tweak the package.json to support both CJS and ESM

[shlomiku]

node 10 eol is in a few months, so that makes sense moving forward. node 12 has more than a year, so it is better to keep that