Update sqlite3_web package#144
Merged
Merged
Conversation
simolus3
commented
May 27, 2026
stevensJourney
approved these changes
May 27, 2026
Contributor
stevensJourney
left a comment
There was a problem hiding this comment.
These are very nice improvements
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
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.
This updates
sqlite3_webto the latest version,0.8.0. That version avoids representing URLs as DartUrito reduce the size of database workers (usingUri.parsepulls in a lot of code). Additionally, it allows using a compile-time option to disable support for DartBigInts (which don't use JS BigInts internally, and also pull a bit of code). For the worker, we can just rely on JS BigInts since that's how clients encode those values inpostMessagecalls. I've added a test using bigints to verify these claims.This update reduces the default worker size from
267,753bytes to213,648, a nice 20% reduction. Unfortunately I doubt we'll see much of an impact on the PowerSync SDK because the sync half of the worker still usesUris.Further, version 0.8.0 replaces the OPFS file system based on atomics and shared array buffer with a new implementation not requiring those (by lazily opening files when a database lock is acquired). This only affects Safari because we can use OPFS in shared workers on Firefox and
readwrite-unsafeon Chrome, but this finally means OPFS is available in all major browsers without additional setup.I've disabled the
build_runner teststep due to a bug in recentbuild_runnerversions (linked from a comment).