Skip to main content

Topic

JSON

4 ZeroUtil articles cover JSON, published between March 2026 and August 2026. Each one is written to explain the mechanism rather than list steps, and links to the free browser tools that do the job.

These articles sit alongside the developer tools toolset.

Article title card. A pair of curly braces containing an amber double slash, with the line: the extension is not the format
Developer Tools

Why tsconfig.json Allows Comments and package.json Does Not

Both files end in .json. One accepts comments and trailing commas, the other throws. The difference is not the extension - it is which parser reads the file.

Article title card. A large pair of amber curly braces, with the line: one format, three dialects
Developer Tools Guide

The Developer's JSON Guide: Everything Worth Knowing About JSON in 2026

The spec, the dialects that disagree, the numbers that quietly break, and the security advice that points at the wrong recursion. With the cluster map.

Article title card. A pair of large curly braces with an amber warning marker dropped between them, with the line: the parser knows where it broke
Developer Tools

Debugging Malformed JSON: A Field Guide

The parse error is better than its reputation. How to read what V8 says now, the five failure modes behind most broken payloads, and the two errors that hide their position.

The words JSON, JSONC and JSON5 stacked in large white type on a dark background, framed by a pair of oversized curly braces
Developer Tools

JSON vs JSON5 vs JSONC: What Each Parser Actually Accepts

Three formats, one file extension, and no agreement on what counts as valid. Measured against the real parsers, including two that disagree while being the same library.