Reconcile-text: conflict-free 3-way text merging

Think diff3 or git merge, but with intelligent conflict resolution that just works.

Reconcile is a Rust and JavaScript (via WebAssembly) library that merges conflicting text edits without requiring manual intervention. Where traditional 3-way merge tools would leave you with conflict markers to resolve by hand, Reconcile automatically weaves changes together using sophisticated algorithms inspired by Operational Transformation.

✨ Try the interactive demo to see it in action!

Find it on:

What makes Reconcile special?

🚫 No conflict markers — Clean, merged output without Git's <<<<<<< noise
📍 Cursor tracking — Automatically repositions cursors and selections during merging
🔧 Flexible tokenisation — Word-level (default), character-level, or custom strategies
🌍 Unicode-first — Full UTF-8 support
🕸️ Cross-platform — Native Rust performance with WebAssembly for JavaScript

Quick start

Rust

Run cargo add reconcile-text or add reconcile-text to your Cargo.toml:

[dependencies]
reconcile-text = "0.4"

Then merge away:

use reconcile_text::{reconcile, BuiltinTokenizer};

// Start with original text
let parent = "Hello world";
// Two people edit simultaneously
let left = "Hello beautiful world";  // Added "beautiful"
let right = "Hi world";              // Changed "Hello" to "Hi"

// Reconcile combines both changes intelligently
let result = reconcile(parent, &left.into(), &right.into(), &*BuiltinTokenizer::Word);
assert_eq!(result.apply().text(), "Hi beautiful world");

JavaScript/TypeScript

Install via npm:

npm install reconcile-text

Then use in your application:

import { init, reconcile } from 'reconcile-text';

// Same example as above
const parent = 'Hello world';
const left = 'Hello beautiful world';
const right = 'Hi world';

const result = reconcile(parent, left, right);
console.log(result.text); // "Hi beautiful world"

Advanced usage

Edit provenance

Track which changes came from where using reconcileWithHistory:

const result = reconcileWithHistory(parent, left, right);
console.log(result.history); // Detailed breakdown of each text span's origin

Tokenisation strategies

Reconcile offers different ways to split text for merging:

Word tokeniser (BuiltinTokenizer::Word) — Splits on word boundaries (recommended for prose)
Character tokeniser (BuiltinTokenizer::Character) — Individual characters (fine-grained control)
Line tokeniser (BuiltinTokenizer::Line) — Line-by-line (similar to git merge or more precisely git merge-file)
Custom tokeniser — Roll your own for specialised use cases

Cursor tracking

Ideal for collaborative editors — Reconcile tracks cursor positions through merges:

const result = reconcile(
  'Hello world',
  {
    text: 'Hello beautiful world',
    cursors: [{ id: 1, position: 6 }], // After "Hello "
  },
  {
    text: 'Hi world',
    cursors: [{ id: 2, position: 0 }], // At the beginning
  }
);

// Cursors are automatically repositioned in the merged text
console.log(result.cursors); // [{ id: 1, position: 3 }, { id: 2, position: 0 }]

How it works

Reconcile builds upon the foundation of diff3 but adds intelligent conflict resolution. Given a parent document and two modified versions (left and right), here's what happens:

Diff computation — Myers' algorithm calculates differences between (parent ↔ left) and (parent ↔ right)
Tokenisation — Text splits into meaningful units (words, characters, etc.) for granular merging
Diff optimisation — Operations are reordered and consolidated to maximise coherent changes
Operational Transformation — Edits are woven together using OT principles, preserving all modifications

Whilst Reconcile's primary goal isn't implementing Operational Transformation, OT provides an elegant way to merge Myers' diff output. The same could be achieved with CRDTs, though the quality depends entirely on the underlying 2-way diffs. Note that move operations aren't supported, as Myers' algorithm decomposes them into separate insert and delete operations.

Why Reconcile exists

Collaborative editing is everywhere — multiple users editing documents simultaneously, or the same person working across devices. This creates the inevitable challenge of conflicting changes.

Traditional solutions like CRDTs or Operational Transformation work brilliantly when you control the entire editing environment. They capture every keystroke, cursor movement, and operation. But real-world workflows are messier: users love tools that don't lock them in. Take Obsidian's approach with plain Markdown files — users can edit with any tool they fancy, from Vim to Word.

This creates what's known as Differential Synchronisation ¹: you only know the final state of each document, not how it got there. It's the same challenge Git tackles, but Git expects humans to resolve conflicts manually.

Here's the key insight: whilst incorrect merges in source code can introduce devastating bugs, human text is more forgiving. People excel at extracting meaning from imperfect text — a slightly clumsy sentence is preferable to conflict markers interrupting the flow.

Caveat: Some text domains are less tolerant of imperfect merges. Legal contracts, for instance, could have unintended meaning changes from double-negations created by conflicting edits.

Development

Prerequisites

Node.js setup

Install nvm:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash

Install and use Node 22:
```
nvm install 22 && nvm use 22
```
Optionally set as default: nvm alias default 22

Rust toolchain

Install rustup:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Install additional tools:

cargo install wasm-pack cargo-insta cargo-edit

Development scripts

Run tests: scripts/test.sh
Lint and format: scripts/lint.sh
Build demo website: scripts/dev-website.sh
Build demo website: scripts/build-website.sh
Publish new version: scripts/bump-version.sh patch

License

MIT

reconcile-text 0.4.8