Loro Inspector is here! Now you can directly browse the current state and complete edit history of your Loro documents in the browser. You can also use this tool to time travel to any version in the history of your Loro document.
30.04.2025 07:28 — 👍 19 🔁 4 💬 1 📌 0
New version control primitives have been added to Loro:
- diff(from, to): calculate the differences between any two versions
- revertTo(version): Generate ops to revert to the target version
- applyDiff(diff): Apply differences
You can use them to implement functions like git squash and revert.
09.01.2025 08:48 — 👍 14 🔁 3 💬 1 📌 0
The slides for the talk are available here: loro-slidev.vercel.app
26.11.2024 19:05 — 👍 12 🔁 4 💬 0 📌 0
Container Overwrites
When initializing child containers in parallel, overwrites can occur instead of automatic merging. For example:
const doc = new LoroDoc();
const map = doc.getMap("map");
// Parallel initialization of child containers
const docB = doc.fork();
const textA = doc.getMap("map").setContainer("text", new LoroText());
textA.insert(0, "A");
const textB = docB.getMap("map").setContainer("text", new LoroText());
textB.insert(0, "B");
doc.import(docB.export({ mode: "update" }));
// Result: Either { "meta": { "text": "A" } } or { "meta": { "text": "B" } }
This behavior can lead to serious data loss issues. If a container holds significant data or even the entire document's content, overwriting it could result in unexpected loss of important information. While the complete editing history is preserved and allows for potential recovery of user data, the recovery process can be complex.
You may experience data loss due to the following issues caused by incorrect usage of CRDTs libraries, regardless of whether you're using Loro, Automerge, or Yjs. Here is how to avoid them:
06.11.2024 11:34 — 👍 10 🔁 1 💬 2 📌 1
