fix: bump better-sqlite3 to 12.11.1 for Node 26 compatibility - #1036
Merged
Merged
Conversation
…n engines to >=20
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.
Users on Node 26 hit
EBADENGINEwhen installing vianpx cve-lite-clibecausebetter-sqlite3@12.9.0does not declare26.xin its engines field.Bumps
better-sqlite3from12.9.0to12.11.1, which adds Node 26 to its supported engines. Also tightens our ownengines.nodefrom>=18to>=20to match whatbetter-sqlite312.x actually supports - v13 raises the floor to>=22, so12.11.1is the right pick to keep Node 20 users unaffected.Closes #1035