Written by Sam Taylor — Full-Stack Developer. I build tools that solve real problems. More about me →
A deployment failed because a config file had a trailing comma after the last array element. The error message was "Unexpected token" with no line number. Two developers spent 10 minutes looking at the file before I pasted it into Formly's JSON validator. It highlighted line 247, column 3 — the exact trailing comma. Fixed in 30 seconds.
JavaScript lets you put commas after the last array element. JSON does not. A validator catches it instantly. Validate your JSON →
Written by Sam Taylor — Full-Stack Developer. I build tools that solve real problems. More about me →