[diffs/edit] Add edit prediction support

[ije]

Screen.Recording.2026-07-25.at.02.18.26.mov

Usage:

import type {
  EditorOptions,
  EditPredictProvider,
  EditPredictResponse,
} from '@pierre/diffs/edit';
import { File } from '@pierre/diffs/react';

const provider: EditPredictProvider = {
  async predict(request, { signal }) {
    const response = await fetch('/api/edit-prediction', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify(request),
      signal,
    });

    if (!response.ok) {
      throw new Error('Prediction failed');
    }

    return (await response.json()) as EditPredictResponse;
  },
};

const editorOptions: EditorOptions<undefined> = {
  editPrediction: {
    provider,
    mode: 'eager',
    include: ['**/*.ts', '**/*.tsx'],
    exclude: ['**/*.test.ts'],
  },
};

export function EditableFile() {
  return (
    <File
      file={{
        name: 'cart.ts',
        contents: 'const total = items.',
      }}
      edit
      editorOptions={editorOptions}
    />
  );
}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
pierre-docs-diffs	Ready	Preview	Jul 27, 2026 12:28pm
pierre-docs-diffshub	Ready	Preview	Jul 27, 2026 12:28pm
pierre-docs-trees	Ready	Preview	Jul 27, 2026 12:28pm
pierrejs-diff-demo	Ready	Preview	Jul 27, 2026 12:28pm

[ije]

@codex review again

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dae253f656

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Support valid edits that share a boundary line

When one non-overlapping edit crosses into a line and the next edit starts later on that same line—for example, {0,2}->{1,0} followed by {1,1}->{1,2}—the previous render edit ends on line, so this branch returns from the response handler. The public provider contract permits non-overlapping edit batches, but this valid response is silently discarded: no preview appears and Tab cannot accept it. Compose the boundary-line overlays or otherwise render the batch without rejecting it.

Useful? React with 👍 / 👎.

[ije]

fixed in 0b00db6

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​vercel/​firewall@​1.2.1

View full report

[fat]

@ije can you add an example to the playground for this as well? that way we can make sure it works with virtualization libraries, etc