Env Diff

A `.env` file, an nginx config, a systemd unit — none of it is JSON, so a structural diff has nothing to walk. A line diff is the right tool for exactly this shape: compare two versions of a text file line by line and show what moved, without needing to understand the file's grammar at all.

Matched by content, not by line number

This finds the longest run of lines both files share in the same order and reports everything outside that run as added or removed — the same method diff and every version control system use. A single line inserted near the top does not cascade into every later line reading as "changed," the way a naive position-by-position comparison would.

Every line, not just values

Unlike the `.env` Validator or the Env File Converter, this does not parse KEY=value pairs — it compares raw lines. That is deliberate: a config file's comments, blank-line spacing and key ordering are often exactly what changed, and a parser that normalised those away before comparing would hide the edit you're looking for.

Changing PORT=8080 to PORT=3000 reports one removed line and one added line, even though only the value changed — a line diff has no concept of "the same key with a different value," only whole lines that match or don't.