Validate JSON and find the exact broken token.
Strict parsing with line and column diagnostics, plus sorted keys for easier review.
{ "deploy": { "env": { "LOG_LEVEL": "debug", "TIMEOUT_MS": 2500 }, "health": true, "notes": null, "region": "eu-west-1", "replicas": 3, "service": "api-gateway" } }
# 13 lines · 208 chars
01 · How validation works
Strict grammar, precise error location.
A JSON validator does one job well: decide whether a string parses, and if not, say exactly where it broke. jsonglow reports the first offending token with its line and column so you can jump straight to it in your editor.
Common failures are trailing commas, single quotes around keys or strings, unescaped newlines inside strings, and stray comments copied from a config file. Each of these fails the specification even though many languages accept them.
02 · Capabilities
Diagnostics built for debugging real payloads.
Line and column
Every error carries a precise position, not a vague message.
Sorted key output
Review a validated payload with keys ordered alphabetically.
Tree inspection
Expand nested objects to confirm the shape matches your contract.
03 · FAQ
Quick answers.
What does the validator check?+
It runs a strict JSON parse: quoted keys, no trailing commas, no comments, and valid escape sequences. The first failure is reported with its line and column.
Why does my JSON fail on a trailing comma?+
The JSON specification forbids a comma after the last element of an object or array, even though JavaScript allows it.
Can I validate against a schema?+
Not yet — jsonglow validates syntax, not JSON Schema rules. Structural validation is on the roadmap.
04 · Related tools