// one missing quote, one long night
Your JSON has
a trailing comma.
Paste JSON that a strict parser rejects — trailing commas, single-quoted strings, unquoted keys, // comments, stray semicolons — and Delint JSON repairs what it can, then pretty-prints the result.
What gets fixed
- Trailing commas — the extra comma before a closing
]or}that strict JSON doesn't allow - Single-quoted strings — converted to valid double-quoted JSON strings
- Unquoted object keys —
{name: "x"}becomes{"name": "x"} - // and /* */ comments — stripped, since JSON has no comment syntax
- Stray trailing semicolons — removed if the whole payload was pasted with one at the end
Questions
Why doesn't standard JSON allow trailing commas or comments?
JSON was designed as a strict, minimal data-interchange format — no comments, no trailing commas, no unquoted keys. Those are all common in JavaScript object literals, which is where most broken JSON comes from: someone copies a JS object and expects it to parse as JSON.
What if it still can't be fixed?
Some errors are genuinely ambiguous — a missing closing brace, or a string that was never closed — and the tool will tell you it can't auto-repair those. The error message includes the approximate location to check by hand.
Is anything uploaded?
No. Parsing and repair both happen in your browser with JavaScript. Nothing you paste is sent anywhere.