You change one value in a JSON config, run git diff, and get a wall of red and green — because a formatter reflowed the file, or the serializer reordered the keys, or the indentation shifted by two spaces. The one thing you actually changed is buried in there somewhere. Good luck finding it in review.
The problem is that git diff and diff work on lines. JSON isn't lines — it's a tree. So I built jdelta: it compares the data, ignores key order and whitespace entirely, and tells you exactly which values changed, addressed by path. Zero dependencies, no network.
What it looks like
$ jdelta config.before.json config.after.json
Added (1)
