Strict by Accident: Your JSON Parser Isn't Broken — It's Answering the Wrong Que

<p>JSON is the format everyone agrees on. So I wrote 24 awkward but small documents, fed the identical bytes to six parsers on one laptop, and compared what came back.</p> <p>Five

<p>A few weeks ago I ran this through our own JSON repair tool, in the browser, on our own website:<br /> </p> <div class="highlight js-code-highlight"> <pre class="highlight

<p>Two years ago I wrote <a href="https://stepinto.dev/posts/streaming-json-partial-parser/" rel="noopener noreferrer">a partial JSON parser</a> for one job: pulling the

<p>I was building a small app where an LLM returns a recipe as JSON and the UI fills in as the answer streams. Simple idea. It fell over immediately.</p> <p>Here's what my handler

<p>If you work with APIs every day, you've probably had this experience.</p> <p>You copy a JSON response from your browser's DevTools...</p> <p>...and you're greeted by a single

<p>I spent the early 2000s writing parsers. HTML scrapers with regex that would make you cry. XML deserializers that handled seventeen flavours of "valid". CSV readers that knew a

<p>If you’re building APIs, web apps, or mobile apps, you’re probably staring at JSON every single day.</p> <p>Some days you’re just trying to validate a massive API response.

<p>If you work with APIs, configuration files, or frontend applications, you've almost certainly encountered a <strong>JSON parsing error</strong>.</p> <p>Sometimes the error