Add runnable WebSocket sync example - #19
Merged
nmndwivedi merged 1 commit intoSep 19, 2026
Merged
Conversation
|
@pttydou is attempting to deploy a commit to the naman's projects Team on Vercel. A member of the Team first needs to authorize it. |
nmndwivedi
approved these changes
Sep 19, 2026
nmndwivedi
left a comment
Collaborator
There was a problem hiding this comment.
Clean, self-contained example: relay is byte-only, path traversal is guarded, and the undo-isolation test covers the important bit. Lockfile change is just the workspace link (ws was already in the tree). Tests + typecheck pass on top of current main. Thanks!
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.
What & why
Fixes #4.
Adds a runnable sync workspace with two boards connected through a byte-only WebSocket relay. Local user diffs are broadcast with the store's source filter, and received diffs are applied as remote so each client's undo history stays local. This v1 example uses record-level last-writer-wins and intentionally has no persistence or CRDT.
Verified with
npm test,npm run typecheck,npm run build, and a two-client Edge browser smoke test.Checklist
npm testpasses)npm run typecheck)npm run build)@quickdrawjs/core