Looks like the node 22 addition is non-trivial; maybe the 2 changes can be separated?

Looks like the node 22 addition is non-trivial; maybe the 2 changes can be separated?

Sure, for v22 I'll add a separate PR when this is merged.

v18 is EOL in April 25

Should this be merged at the end of April? Then any versions released before then will still have been testing against v18.

v18 is EOL in April 25

Should this be merged at the end of April? Then any versions released before then will still have been testing against v18.

Can be merged anytime (now would be the best time for it).

Let me try to convince you:
At first, it enables us to use some modern API's like URL.parse.

This patch will only affect the next release: PouchDB 10.0.0

It will be a major release and we have the freedom to do breaking changes as we've did it with Node 16 in PouchDB 9, like for example: drop support for Node 18 (very convenient 😉).
No one is forced to update to PouchDB 10.

PouchDB 9 is stable and nobody complains about security bugs (so far).
Iff someone find a vulnerability before 18 goes EOL, we can branch from https://github.com/pouchdb/pouchdb/tree/9.0.0 at any time to patch up a version 9.0.1.

Also: I expect that everyone has updated there Node runtime by now (or at least, they are working hard on the transition).