better to testing with nodejs 18

I would say that this adds clarity right -- code is not just read by computers but also by humans, and node 16 will be EOL at some point, and then this could simply be removed again (but only if its clear that it is a node <= 18 thing). I believe I've granted the maintainers access to the branch, so they can make simplifications as they see fit before merging.

Thank you for the PR! And for the write access! I just added a small comment. I'm going to add Node 18 testing to master, merge that in, let tests run, then merge

It would actually be much easier for you to merge in latest master than me, could you whenever you get a chance?

merged and pushed

@thornjad - its merged, in case you missed it

@thornjad - master has been merged

@thornjad it's been over a month,,,;.;

Maintainer is asking for funding but hasn't touched this repo all summer (~3 months)

It seems that this PR is now only needed to support nodejs v18.0.0 - v18.4.0 as they've reverted the change. Would update the version numberrs in the pr.