Migrate from requests to axios

[jesec]

Per suggestion of #144 (review).

[robertsLando]

LGTM

[robertsLando]

@leerob @jesec If it's not clear I'm ok to release a 3.0.0 but I think we firstly need to end this: #135

After that is merged we should bump the version, create a release on github start building the binaries and then once done publish it to npm and bump it in pkg too

[jesec]

I don't think we should release before we got the binaries ready. But we can bump the version.

[robertsLando]

Yeah maybe I explained wrongly I don't want to release it now, I have updated my comment

[jesec]

I can take over the workflow branch, if you don't mind. To start building binaries, we have to be able to pull RHEL tools, per discussions in #124. I have sent necessary info to @leerob .

Additionally, we have to add cross-compiling support (fix Error! Not able to build for 'arm64' here, only for 'x64'). Github Actions don't have arm64 host and emulation is soooo slow.

[robertsLando]

What about using travis for arm64?

[robertsLando]

I can take over the workflow branch, if you don't mind

Sure no problem!

[leerob]

Yes, I will cut a release after we get CI working 👍

[jesec]

Thanks.

I like Github Actions more. I think it could be beneficial to have support for cross-compiling in this project, as well. But yeah, if we do need native, we can use Travis or Azure.

[robertsLando]

I like Github Actions more

Me too but AFAIK there is no arm64 suppport in available runners yet. We could ask @leerob if @vercel can provide us a custom arm64 runner for this purpose

[leerob]

Would like to stick with GitHub Actions if at all possible. Could we enumerate the pros/cons in the CI PR?

[leerob]

If it's possible to get a custom arm runner, let me know and send some docs and I can ask!

[robertsLando]

@leerob Here you are: https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners

[leerob]

Let's start with getting GH Actions CI working and then I will explore this! Thank you!