Raise the supported Node.js runtime so the project can rely on the stabilized node:sqlite API and use one consistent Node 24 runtime for local development, CI, and containers.
Version policy
Set the package engine constraint to:
>=24.15.0 <25 || >=25.7.0
If the first Node 24 LTS release is greater than 24.15.0, use that first-LTS version as the lower bound instead. In other words, the Node 24 lower bound is the greater of 24.15.0 and the first 24.x LTS release; supported 25.x versions begin at 25.7.0.
For reproducible project tooling:
Add/update .node-version to the latest available Node 24.x release at implementation time for fnm and other version-file consumers.
Make CI use .node-version as its Node version source.
Update the server Dockerfile introduced by #7 to use the same exact Node 24.x release in every stage, rather than an independent floating or stale version.
Scope
Update package.json engine metadata and regenerate lockfile metadata as needed.
Verify native-free SQLite operation through node:sqlite on the selected baseline.
Acceptance criteria
The Node engine range implements the policy above and rejects unsupported Node versions below both baselines.
.node-version pins the latest available 24.x release selected when the change lands.
CI uses that version and passes install, build, typecheck, lint, format, and tests.
The Docker build uses the same exact 24.x version in all Node stages.
Local setup and deployment documentation state both the supported range and the pinned default.
node:sqlite runs without experimental warnings on the pinned baseline.
The selected version unblocks removal of better-sqlite3 in the dependent issue.
## Goal
Raise the supported Node.js runtime so the project can rely on the stabilized `node:sqlite` API and use one consistent Node 24 runtime for local development, CI, and containers.
## Version policy
Set the package engine constraint to:
```text
>=24.15.0 <25 || >=25.7.0
```
If the first Node 24 LTS release is greater than `24.15.0`, use that first-LTS version as the lower bound instead. In other words, the Node 24 lower bound is the greater of `24.15.0` and the first 24.x LTS release; supported 25.x versions begin at `25.7.0`.
For reproducible project tooling:
- Add/update `.node-version` to the latest available Node 24.x release at implementation time for fnm and other version-file consumers.
- Make CI use `.node-version` as its Node version source.
- Update the server Dockerfile introduced by #7 to use the same exact Node 24.x release in every stage, rather than an independent floating or stale version.
## Scope
- Update `package.json` engine metadata and regenerate lockfile metadata as needed.
- Add or update `.node-version`.
- Update developer and deployment documentation.
- Update CI setup from #4 to consume `.node-version`.
- Coordinate the exact Docker base tag with #7.
- Verify native-free SQLite operation through `node:sqlite` on the selected baseline.
## Acceptance criteria
- The Node engine range implements the policy above and rejects unsupported Node versions below both baselines.
- `.node-version` pins the latest available 24.x release selected when the change lands.
- CI uses that version and passes install, build, typecheck, lint, format, and tests.
- The Docker build uses the same exact 24.x version in all Node stages.
- Local setup and deployment documentation state both the supported range and the pinned default.
- `node:sqlite` runs without experimental warnings on the pinned baseline.
- The selected version unblocks removal of `better-sqlite3` in the dependent issue.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Raise the supported Node.js runtime so the project can rely on the stabilized
node:sqliteAPI and use one consistent Node 24 runtime for local development, CI, and containers.Version policy
Set the package engine constraint to:
If the first Node 24 LTS release is greater than
24.15.0, use that first-LTS version as the lower bound instead. In other words, the Node 24 lower bound is the greater of24.15.0and the first 24.x LTS release; supported 25.x versions begin at25.7.0.For reproducible project tooling:
.node-versionto the latest available Node 24.x release at implementation time for fnm and other version-file consumers..node-versionas its Node version source.Scope
package.jsonengine metadata and regenerate lockfile metadata as needed..node-version..node-version.node:sqliteon the selected baseline.Acceptance criteria
.node-versionpins the latest available 24.x release selected when the change lands.node:sqliteruns without experimental warnings on the pinned baseline.better-sqlite3in the dependent issue.