chore: migrate to Node 24 LTS and replace sqlite3 with node:sqlite#422
Closed
YagUber wants to merge 3 commits intocedya77:devfrom
Closed
chore: migrate to Node 24 LTS and replace sqlite3 with node:sqlite#422YagUber wants to merge 3 commits intocedya77:devfrom
YagUber wants to merge 3 commits intocedya77:devfrom
Conversation
Bump base Docker image and .nvmrc to node:24-alpine / 24. Node 20 enters end-of-life April 2026. Node 24 is the current Active LTS through April 2028.
Remove unmaintained sqlite3 npm package in favor of the native node:sqlite module introduced in Node.js 22 and available without a flag in Node 24.
Contributor
Author
|
Addressed by #423 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sqlite3is no longer maintained and its README recommends migrating away from it.node:sqliteis currently at Stability 1.2 (release candidate). It will emit an ExperimentalWarning at runtime until it reaches stable. The API surface used here (DatabaseSync, prepare, run, get, all) is unlikely to change before stabilization.better-sqlite3was considered as an alternative, but I figured being an early adopter of the built-in module couldn't hurt here.Tested against the SQLite path locally, all read/write/upsert/delete operations work as expected.
Changes
sqlite3package in favor of the built-innode:sqlitemodule introduced in Node.js 22 and available without flags in Node 24