chore: remove semver dependency

[rtritto]

Simplify logic to check Node version and remove the use of semver dependency.

Fix #516

[erickzhao]

Hi @rtritto, thanks for the PR. I think we should instead just add semver as a dep here instead of manually parsing the version string.

We already have semver in our lockfile a couple times, so I think this would be the correct invocation:

yarn add semver
npx uuaw semver

[rtritto]

It's better to have less dependencies to reduce version checks and to improve performance, bundle and readability.
In the future, semver could be removed from other dependencies and, with this change, we won't change nothing.

[erickzhao]

It's better to have less dependencies to reduce version checks and to improve performance, bundle and readability.

I disagree here. SemVer logic isn't always trivial and having to write individual string parsing functions for each case doesn't make a lot of sense.

It's also a first-party npm package that's used across the ecosystem (for example, we already have a few other instances of semver in this project's lockfile via tooling such as typescript-eslint).

[MarshallOfSound]

Agree with Erick above, also worth noting that this code as it stands is wrong. Difference checks between numbers and strings do not work as you'd expect.

Keep the semver dependency

[rtritto]

Agree with Erick above, also worth noting that this code as it stands is wrong. Difference checks between numbers and strings do not work as you'd expect.

You're right, I forgot the compare as numbers with parseInt.

Opened #535