End of input while parsing an object (missing '}') at line L,15
This message comes from hjson on Node.js 22.22.2. In this registry it is produced by 2 distinct mistakes. Positions in the real message vary with your input; the causes do not.
Causes
What produces this message
Infinity is not valid JSON
Input
{"a": Infinity}Exact message: End of input while parsing an object (missing '}') at line 1,15 >>>"a": Infinity} ...
Fix: Write `null`, a string, or clamp the value before serialising. Python: `json.dumps(x, allow_nan=False)`.
Missing comma between object members
Input
{"a": 1 "b": 2}Exact message: End of input while parsing an object (missing '}') at line 1,15 >>>"a": 1 "b": 2} ...
Fix: Add a comma between the two members.
Same bug, other languages
What other parsers say about the same input
If a colleague reports a different message for what looks like the same file, this is why.
| Parser | Message for the same inputs |
|---|---|
| CPython json.loads | Expecting ',' delimiter: line L column C (char N) |
| Gson | Unterminated object at line L column C path $… |
| Gson JsonParser (lenient off) | Unterminated object at line L column C path $… |
| JSON5 | JSON5: invalid character '\"' at 1:9 |
| JSON::PP | , or } expected while parsing object/hash, at character offset N (before "…")malformed JSON string, neither array, object, number, string or atom, at character offset N (before "…") |
| Jackson ObjectMapper | Non-standard token 'Infinity': enable `JsonReadFeature.ALLOW_NON_NUMERIC_NUMBERS` to allowUnexpected character ('"' (code 34)): was expecting comma to separate Object entries |
| JavaScriptCore JSON.parse | JSON Parse error: Expected '}'JSON Parse error: Unexpected identifier "Infinity" |
| Newtonsoft.Json JsonConvert | After parsing a value an unexpected character was encountered: ". Path 'a', line L, position N. |
| Newtonsoft.Json JsonTextReader | After parsing a value an unexpected character was encountered: ". Path 'a', line L, position N. |
| Ruby JSON.parse | unexpected token at '…' |
| SpiderMonkey JSON.parse | JSON.parse: expected ',' or '}' after property value in object at line L column C of the JSON dataJSON.parse: unexpected character at line L column C of the JSON data |
| System.Text.Json Deserialize | '"' is invalid after a value. Expected either ',', '}', or ']'. Path: $ | LineNumber: L | BytePositionInLine: C.'I' is an invalid start of a value. Path: $ | LineNumber: L | BytePositionInLine: C. |
| System.Text.Json JsonDocument | '"' is invalid after a value. Expected either ',', '}', or ']'. LineNumber: L | BytePositionInLine: C.'I' is an invalid start of a value. LineNumber: L | BytePositionInLine: C. |
| V8 JSON.parse | Expected ',' or '}' after property value in JSON at position N (line L column C)Unexpected token 'I', "{"a": Infinity}" is not valid JSON |
| encoding/json Unmarshal | invalid character '"' after object key:value pairinvalid character 'I' looking for beginning of value |
| json-bigint | Expected ',' instead of '"'Unexpected 'I' |
| json_decode | Syntax error |
| orjson | unexpected character, expected ',' or '}': line L column C (char N)unexpected character, expected a JSON value: line L column C (char N) |
| serde_json::from_str | expected `,` or `}` at line L column Cexpected value at line L column C |
| ujson | Unexpected character in found when decoding object value |
Sources
Standards this registry is checked against
- RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The IETF Internet Standard for JSON. Obsoletes RFC 7159 and RFC 4627.
- ECMA-404, 2nd edition — The JSON Data Interchange Syntax, Ecma International, 2017. Ecma’s grammar for JSON. A normative reference of RFC 8259; the two define the same syntax.
- The Unicode Standard — The Unicode Standard, Core Specification, The Unicode Consortium, current. Normatively referenced by RFC 8259 for the definition of a character.
- IEEE 754-2019 — IEEE Standard for Floating-Point Arithmetic, IEEE, 2019. Referenced by RFC 8259 §6 as the basis for its interoperability guidance on numbers.
Only standards bodies and peer-reviewed venues are cited. Error strings on this site are observed by executing each parser; the standards above define what the parser is reacting to.