Earlier quoted context omitted.
ISTM one could keep developing for the old nodejs under the current major version, or even the current major version plus a few more major versions. Then simultaneously release under a different major version for the new nodejs. The "engines" option of package.json makes it possible to partition one's releases this way. This may end up deviating a bit from semver, but node and npm have long done that themselves. Idea…
Does "engines" actually make it possible to partition your releases? I thought by default the engines part of packages.json was ignored.
Whoops, you're right. I guess there must be good reasons for that default. Maybe there has to be some version-checking in the API-using code itself. That makes it an even better idea to isolate that shit in a separate module.