<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Json on Dev Journal</title><link>https://rajkumargosavi.github.io/tags/json/</link><description>Recent content in Json on Dev Journal</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 21 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rajkumargosavi.github.io/tags/json/index.xml" rel="self" type="application/rss+xml"/><item><title>JSON Explorer</title><link>https://rajkumargosavi.github.io/projects/json-explorer/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://rajkumargosavi.github.io/projects/json-explorer/</guid><description>&lt;p align="center">
 &lt;img src="https://raw.githubusercontent.com/rajkumarGosavi/json-explorer/main/src-tauri/icons/128x128%402x.png" alt="JSON Explorer" width="96" height="96">
&lt;/p>
&lt;h1 align="center">JSON Explorer&lt;/h1>
&lt;p align="center">&lt;strong>Open the JSON file your editor can't.&lt;/strong>&lt;br>
Drop in a multi-gigabyte JSON or NDJSON file and browse it in a fast, virtualized tree — no waiting for the whole thing to load.&lt;/p>
&lt;p align="center">
 &lt;a href="https://github.com/rajkumarGosavi/json-explorer/releases/latest" target="_blank" rel="noopener noreferrer">&lt;strong>⬇️ Download latest&lt;/strong>&lt;/a> ·
 &lt;a href="https://github.com/rajkumarGosavi/json-explorer" target="_blank" rel="noopener noreferrer">Source on GitHub&lt;/a> ·
 &lt;a href="https://github.com/rajkumarGosavi/json-explorer/issues" target="_blank" rel="noopener noreferrer">Report an issue&lt;/a>
&lt;/p>
&lt;hr>
&lt;h2 id="why-this-project-was-needed">Why this project was needed&lt;/h2>
&lt;p>Working with data means constantly running into JSON files that are too big to open — an API dump, a database export, a log of NDJSON events. Every obvious tool falls over: the text editor freezes, the browser tab crashes, &lt;code>jq&lt;/code> gets you a slice but not a way to &lt;em>browse&lt;/em>, and &amp;ldquo;online JSON viewers&amp;rdquo; are a non-starter for anything sensitive or large. The usual workaround is writing a throwaway script just to peek at the shape of the data — which is a lot of friction for a question as simple as &amp;ldquo;what&amp;rsquo;s actually in this file?&amp;rdquo;&lt;/p></description></item></channel></rss>