Migration to Node v24.13.0 which is the LTS release - All new development should be targeted at least the LTS versions of stack dependencies #15
Conversation
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
added 3 commits
January 21, 2026 14:27
Updated better-sqlite3 to v12.x.x requiring more stringent special character checks to meet the new stricter fts5 query formatting requirements.
- src/memory/search.js and src/memory/tools.js were both refactored to enhance robustness and achive the stringency requirements.
…up unit tests to avoid environment polution
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.
Here, we address the better-sqlite3 versioning issue which precluded deployment using node v24. The solution likely also addresses #5 where the primary reported issue related ot tree-sitter but it appears that element of the dependency issue was either resolved in a commit over the past two days, or was itself a red herring. In any case, I expect the node v24 migration will effectively resolbe the depencency issues reported with node v23 as well, although, as a general principle, we should be using at least the newest LTS release of node for any new development.