Bump @treecrdt/wa-sqlite to 0.3.2 - #91
Merged
Merged
Conversation
marcus-pousette
force-pushed
the
fix/wa-sqlite-shared-worker-persistence
branch
from
July 14, 2026 10:56
c6550d0 to
ce2befc
Compare
Antonov548
approved these changes
Jul 14, 2026
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.
Summary
@treecrdt/wa-sqlitedependency from 0.3.1 to 0.3.2Why
The production
sqlite3_open_v2failure came from the old wa-sqlite OPFS pathname limit. cybersemics/treecrdt#213 fixes that limit and was released in 0.3.2.The exact long-path lifecycle regression remains at the library layer in cybersemics/treecrdt#221.
Follow-up coverage
The em SharedWorker + OPFS coverage improvements were extracted into the stacked #92, keeping this production fix minimal.
Verification
@treecrdt/wa-sqlite@0.3.2