JsonForge · JSON errors
Comments are not allowed in JSON
JSON has no comment syntax. Files that look like JSON but carry comments are JSON5 or JSONC — tsconfig.json is JSONC, which is why editors accept it and JSON.parse does not.
The smallest input that causes it
{
// the id
"id": 1
}JSON.parse on that gives, verbatim:
Expected property name or '}' in JSON at position 4 (line 2 column 3)
The fix
{"id": 1}That version parses.
Find it in your own document
Paste the JSON and get the error located by line and column, the document formatted, a schema inferred from it, and a diff against another version.
Open JsonForgeOther JSON errors
- Unexpected end of JSON input
- Unexpected token '<', "<html>" is not valid JSON
- "undefined" is not valid JSON
- Expected double-quoted property name in JSON
- Expected property name or '}' in JSON at position 1
- Single quotes are not valid JSON
- Unexpected non-whitespace character after JSON
- Unexpected number in JSON
- Bad control character in string literal in JSON
- Bad escaped character in JSON