Sync from docs: add InMemoryVFS web option (powersync-docs #538) - #58
Merged
Conversation
michaelbarnes
approved these changes
Aug 18, 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
2 participants
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.
Source docs PR: powersync-ja/powersync-docs#538
What changed in docs
Added documentation for
WASQLiteVFS.InMemoryVFS, a new VFS option in@powersync/web1.39.0+. The option provides non-persistent, fast in-memory storage suited for development and online-only apps.Skill updates in this PR
skills/powersync/references/sdks/powersync-js.md: AddedInMemoryVFSto the VFS options table and a guidance block covering when to use it, multi-tab behavior on Chrome and Firefox Desktop, the tab-isolation pattern, and theps_crudmonitoring caveat for production use.Notes for reviewer
The skill update captures the decision-relevant facts an agent needs: when to recommend InMemoryVFS, when not to (offline support required), the multi-tab shared-worker default, and the production caveat around unsynced writes. The tab-isolation code example is taken directly from the docs. No new skill file was needed; the existing VFS section in
powersync-js.mdwas the right location.Generated by Claude Code