yjs/yjs

Shared data types for building collaborative software

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 2nd, 2026
Created on July 29th, 2014
Open Issues & Pull Requests: 138 (+0)
GitHub issues: Enabled
Number of forks: 801
Total Stargazers: 22,759 (+1)
Total Subscribers: 125 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Yjs is a library for building collaborative applications using shared data types that synchronize across peers.

The library solves the problem of coordinating changes to shared state across multiple clients without requiring a central server. It implements conflict-free replicated data types, allowing offline edits to merge automatically when clients reconnect. The approach works by tracking changes to shared data structures and propagating updates through a network layer that the developer configures, whether peer-to-peer, server-based, or hybrid. Each client maintains its own copy of the data and can apply remote changes in any order while guaranteeing consistency.

Yjs suits projects where real-time collaboration, offline-first functionality, or decentralized architectures matter. It works well for document editors, whiteboards, and any application where multiple users modify shared state simultaneously. Teams building collaborative tools should choose this library if they need automatic conflict resolution without operational transformation complexity. The library is particularly valuable for applications that must work offline and sync changes later, or for peer-to-peer systems where no central authority exists.

The project maintains active development with regular updates addressing edge cases and performance improvements. The codebase shows sustained attention to both core functionality and ecosystem integration, with ongoing refinement of the synchronization protocol and connector implementations. Documentation receives continuous updates to reflect API changes and usage patterns. The maintainers respond to issues and pull requests, indicating engagement with the user community and willingness to address reported problems.