feat: drop Node 4, 6, 8, 10, 12, 14 & 16 support

[MichaelDeBoey]

As @ljharb mentioned in #114 (comment), he's open for a breaking change right now

if eslint forced a breaking change, at that time I’d reevaluate what we supported

---

BREAKING CHANGE: Requires Node@^18.18.0 || ^20.9.0 || >=21.1.0

[MichaelDeBoey]

@ljharb Settings should be updated to make node 18+ required instead of node < 10 & node >= 10

[benmccann]

Node 22 is out, so maybe don't need to support Node 21, which is unstable?

[MichaelDeBoey]

I've set node.engines to the same as ESLint is doing, but I'm happy to update if @ljharb wants to

[talentlessguy]

@MichaelDeBoey could you please update the node range to v22 so it's mergeable?

[ljharb]

@talentlessguy that’s not what’s holding up this PR.

[talentlessguy]

@ljharb what's the problem then?

[ljharb]

the PR is slightly premature. It won't be merged until all the breaking changes are ready, both here and in eslint-plugin-jsx-a11y.

[talentlessguy]

@ljharb which breaking changes should be ready? #142? or some other PR? shouldn't changes first be released in jsx-ast-utils to be incorporated in the updated jsx-a11y plugin?

[MichaelDeBoey]

@ljharb This is the way you requested the PRs on the e18e Discord: add them in small PRs, so they can be reviewed easily

[ljharb]

@MichaelDeBoey yep, and this is perfect once i'm ready :-) you don't need to do anything else.

[talentlessguy]

so in the end what kind of breaking changes have to be done in jsx-ast-utils? I still don't get it

[ljharb]

@talentlessguy for one, I have to make a branch for the major bump, and re-base these PRs onto it, and then I can merge them into that branch. I'll also have to TS-type the whole package, and likely a few other things. But either way, it's not necessary for you to get it, you'll just have to be patient.