<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ankit Agrawal</title>
    <description>The latest articles on DEV Community by Ankit Agrawal (@ankit_agrawal_70d1ecf37a8).</description>
    <link>https://dev.to/ankit_agrawal_70d1ecf37a8</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3754752%2F24f5a008-dba9-4117-b5e5-170d0172e8c4.png</url>
      <title>DEV Community: Ankit Agrawal</title>
      <link>https://dev.to/ankit_agrawal_70d1ecf37a8</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ankit_agrawal_70d1ecf37a8"/>
    <language>en</language>
    <item>
      <title>Stop Scrolling Logs: A Privacy-First Log Viewer for JSON, CSV &amp; Raw Logs</title>
      <dc:creator>Ankit Agrawal</dc:creator>
      <pubDate>Thu, 05 Feb 2026 11:32:01 +0000</pubDate>
      <link>https://dev.to/ankit_agrawal_70d1ecf37a8/stop-scrolling-logs-a-privacy-first-log-viewer-for-json-csv-raw-logs-17i0</link>
      <guid>https://dev.to/ankit_agrawal_70d1ecf37a8/stop-scrolling-logs-a-privacy-first-log-viewer-for-json-csv-raw-logs-17i0</guid>
      <description>&lt;p&gt;When debugging APIs or production issues, I often need to inspect large JSON responses, CSV exports, or raw log files. Most options involve either writing ad-hoc scripts, loading data into heavyweight tools, or uploading sensitive files to third-party services.&lt;/p&gt;

&lt;p&gt;To solve this, I built Log Viewer — a lightweight, client-side log analysis tool that parses JSON, CSV, and unstructured log data directly in the browser and renders it in a searchable, filterable tabular format.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key characteristics:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Runs entirely client-side (no backend processing)&lt;/li&gt;
&lt;li&gt;No authentication or file uploads&lt;/li&gt;
&lt;li&gt;No persistence — files are never stored or transmitted&lt;/li&gt;
&lt;li&gt;Automatic detection of timestamps, nested JSON, and common log patterns&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;👉 &lt;a href="https://logexecute.codeexecute.com/" rel="noopener noreferrer"&gt;https://logexecute.codeexecute.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’m looking for technical feedback from the community:&lt;/p&gt;

&lt;p&gt;Are there additional formats or log schemas worth supporting ?&lt;/p&gt;

&lt;p&gt;Any performance or UX improvements you’d expect when working with large files?&lt;/p&gt;

&lt;p&gt;Features you typically rely on when inspecting logs or structured data?&lt;/p&gt;

&lt;p&gt;The goal is to keep this tool fast, minimal, and privacy-preserving while still being genuinely useful in real debugging workflows.&lt;/p&gt;

&lt;h1&gt;
  
  
  devtools #javascript #webdev #opensource #productivity #developers
&lt;/h1&gt;

</description>
      <category>privacy</category>
      <category>productivity</category>
      <category>showdev</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
