Vector: an open-source issue tracker on TanStack Start, and how it handles stale saves

[zemaj]

Vector is an MIT-licensed issue tracker built on TanStack Start, React and Hono, running on a Cloudflare Worker with D1 for records and R2 for files: https://github.com/just-every/run-vector

I'm James, founder of Just Every, and I made it.

Every incoming report gets a decision (accept, decline, or defer to a date), and a Current list shows each issue in one section with the reason it is there.

The part I'd like Start developers to look at is concurrent editing. Each inline property change (labels, estimate, due date, expected outcome) goes through a version-checked PATCH, and a stale save reports the current server values instead of overwriting. Title and description edit in a separate writing editor that keeps the newest successful save or reload receipt for that issue. Reopening an issue before a background refresh therefore uses its current version, and a genuine conflict keeps the unsaved draft.

You can try it in a minute: open the same issue in two tabs, change a label in the first, change the title in the second before it refreshes, then look at what each tab shows.

It runs locally with npx -y @runeditrun/rer dev just-every/run-vector (Git and Node 22+). Coding agents wrote the code against a written product contract and tests, so the repo also shows what that kind of project looks like.

How do you separate "my write succeeded" from "this read is fresh" in your Start apps? What other ordering case would you add to the two-tab test?