Two weeks ago I published jsonl-utf8-guard , a dependency-free validator for UTF-8 JSONL files. It started as workshop material: a small, offline tool to teach red-to-green regression testing.
Today it got its first two pull requests from someone I had never talked to. A few hours later they were in v0.2.0.
What changed
Both fixes are about one thing: error messages that tell you what is actually wrong.
# before Validation failed: Line 1: invalid JSON
# after Validation failed: Line 1: starts with a UTF-8 byte order mark (BOM) Validation failed: Line 1: contains a bare carriage return; use LF or CRLF line endings
Enter fullscreen mode
Exit fullscreen mode
A BOM is what Windows Notepad and some Excel exports put at the start of a file. A bare carriage return is common in old Mac files and some industrial log exporters. In both cases the JSON itself was fine, and "invalid JSON" sent people looking in the wrong place.
The files are still rejected, so the behavior is unchanged.…