Version floor conflict

[StoneCypher]

Two libraries we've added - babel and nve - require core-js.

Core-js has a node floor of 12, but we offer a node floor of 10. As a result, our node 10 builds are breaking.

We are already getting rid of nve, and I think we're considering switching from babel to typescript for downcompiling

May I temporarily remove the 10.x claim from the build, with the goal of re-adding it once babel is out?

[hildjj]

nve is removed in #89

[hildjj]

yes, you can update to >=12, with the idea that we won't release anything where that lands until 2021-05-01 or later.

[StoneCypher]

nve is removed in #89

It's still in package-lock. I'll fix it

[StoneCypher]

yes, you can update to >=12, with the idea that we won't release anything where that lands until 2021-05-01 or later.

I mean, honestly, I still kind of want to support 10

I just want to reduce the claim for a couple days while I get the underlying breakage fixed

[hildjj]

gah, sorry I missed updating package-lock. fixing it in my PR.

[StoneCypher]

forgetting package-lock is the second most common mistake i make in node, behind forgetting to rebuild before pushing 😂

[hildjj]

Hm. I just regenerated package-lock from scratch, git diff doesn't show a change. Maybe I got this in the latest rebase I just pushed?

[StoneCypher]

easiest way to check is probably cat package-lock.json | grep core-js

[hildjj]

        "core-js-compat": "^3.9.0",
        "core-js-compat": "^3.9.1"
    "node_modules/core-js-compat": {
      "resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.10.2.tgz",
        "url": "https://opencollective.com/core-js"
    "node_modules/core-js-compat/node_modules/semver": {
        "core-js-compat": "^3.9.0",
        "core-js-compat": "^3.9.1"
    "core-js-compat": {
      "resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.10.2.tgz",