chore: drop support for Node.js v10

[theoludwig]

What changes did you make? (Give an overview)

• Drop support for Node.js v10
• Add Node.js v16 to the node-version matrix in CI with GitHub Actions

Is there anything you'd like reviewers to focus on?

BREAKING CHANGE: Minimum supported Node.js version >= 12.0.0

[voxpelli]

We may want to require one of the later Node 12 releases, to be able to use all the newest features in it, just like we did with Node 10

[theoludwig]

We may want to require one of the later Node 12 releases, to be able to use all the newest features in it, just like we did with Node 10

Yes, do you have a specific Node.js v12 version in particular we could require ?

[voxpelli]

I tried finding a good comparison, but eg https://node.green/ has no easy way to just compare two versions, so right now I don't know if there's any substantial new addition language wise.

And haven't checked the Node.js API additions at all.

[theoludwig]

I tried finding a good comparison, but eg node.green has no easy way to just compare two versions, so right now I don't know if there's any substantial new addition language wise.

And haven't checked the Node.js API additions at all.

Right, I think it is not necessary to require a newer Node.js v12 version if we don't need it.
I think it is fine to require Node.js >=12.0.0.

EDIT: To ease the migration from CommonJS to ESM, I suggest to support these Node.js versions: "^12.20.0 || ^14.13.1 || >=16.0.0", so we will be able to import builtin modules like fs etc. like this : import fs from 'node:fs'.
Ref: sindresorhus/meta#15 (comment)

[voxpelli]

Some thoughts, sorry for the slow review, I will try to be quicker 🙈

[LinusU]

Great! 👍

Since this is a breaking change I think that we should also convert to ESM before cutting the next release. I can submit a PR unless someone else is working on it ☺️

[voxpelli]

@LinusU We had planned doing that for 16.0.0: https://github.com/standard/standard-engine/milestone/2

[voxpelli]

Focusing on this for 15.0.0: https://github.com/standard/standard-engine/milestone/1

[theoludwig]

Great!

Since this is a breaking change I think that we should also convert to ESM before cutting the next release. I can submit a PR unless someone else is working on it

Yes, you can open a PR. 😄
But as @voxpelli said, currently it is planned for v16 to avoid too much BREAKING CHANGE in one single release (v15), but we can discuss that again in #251.