Please add "engines" config to package.json

[benjamincburns]

Given that most major releases are due to changes in what node and/or electron versions are supported by this library, it would be helpful if these details were captured in the package.json engines config.

Admittedly this field is only advisory, but it would help package maintainers who depend on better-sqlite3 to choose the correct version range(s) for the engines that we're trying to support.

[mceachen]

I think this is totally reasonable.

FWIW we have to be pretty conservative with what node versions we support, given that we build more than 100 different precompiled artifacts for every release.

We enjoy an embarrassment of riches of issues opened for better-sqlite3 versions from the late Cenozoic--this may help stem that tide.

[wolfgang42]

Looking at the build workflow:

better-sqlite3/.github/workflows/build.yml

Line 18 in df8a6a4

NODE_BUILD_CMD: npx --no-install prebuild -r node -t 18.0.0 -t 20.0.0 -t 22.0.0 -t 23.0.0 --include-regex 'better_sqlite3.node$'

I think the correct value is just

"engines": {                                                                                                                                                                                                     
  "node": "18.x || 20.x || 22.x || 23.x"                                                                                                                                                                         
} 

Anything I’m missing that might mean this needs to be more specific?