Written by Sam Taylor — Full-Stack Developer. I build tools that solve real problems. Formly is one of them. More about me →
A deployment failed last week because a config file had a trailing comma after the last array element. The error message said "Unexpected token" with no line number. Two of us stared at the file for ten minutes before I pasted it into Formly's JSON validator. It highlighted line 247, column 3 — the exact trailing comma. We fixed it and redeployed in under a minute.
JSON does not allow trailing commas. Most programming languages do, so developers add them out of habit. The parser rejects the entire file, and the error message rarely points to the right line. A validator catches it instantly. Validate your JSON →
Written by Sam Taylor — Full-Stack Developer. I build tools that solve real problems. Formly is one of them. More about me →