<?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: Harshit Duggal</title>
    <description>The latest articles on DEV Community by Harshit Duggal (@harshitduggal).</description>
    <link>https://dev.to/harshitduggal</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4243361%2F3c221db9-f3ad-4a6f-a71b-b5fd422a66b8.png</url>
      <title>DEV Community: Harshit Duggal</title>
      <link>https://dev.to/harshitduggal</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/harshitduggal"/>
    <language>en</language>
    <item>
      <title>I built a local-first markdown editor. Here's what kept it fast on huge docs</title>
      <dc:creator>Harshit Duggal</dc:creator>
      <pubDate>Fri, 20 Nov 2026 08:38:05 +0000</pubDate>
      <link>https://dev.to/harshitduggal/i-built-a-local-first-markdown-editor-heres-what-kept-it-fast-on-huge-docs-184f</link>
      <guid>https://dev.to/harshitduggal/i-built-a-local-first-markdown-editor-heres-what-kept-it-fast-on-huge-docs-184f</guid>
      <description>&lt;p&gt;Flow is a local-first markdown workspace that runs entirely in your browser. No account, no sign-up, no server holding your notes. You open it, write, and your docs stay in IndexedDB on your machine.&lt;/p&gt;

&lt;p&gt;Live: &lt;a href="https://markdown-editor.opalhq.fun/" rel="noopener noreferrer"&gt;https://markdown-editor.opalhq.fun/&lt;/a&gt;&lt;br&gt;
Repo: &lt;a href="https://github.com/duggal1/markdown-editor" rel="noopener noreferrer"&gt;https://github.com/duggal1/markdown-editor&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I built it because I kept losing time to editors that asked for a login before I could type a heading, and because a lot of what I write is drafts I would rather not send anywhere. Local-first made that a property of the app instead of a line in a privacy policy.&lt;/p&gt;

&lt;p&gt;Three engineering decisions did most of the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Virtualized preview, search in a web worker
&lt;/h2&gt;

&lt;p&gt;Big docs are where most browser editors fall apart. The preview and the code pane are virtualized with TanStack Virtual, so only the rows in view are in the DOM. Updates are deferred and markdown is processed in chunks. Search and word count run in a web worker, so typing stays responsive while a large file is scanned. The editor is CodeMirror 6 with write, split and preview modes and GitHub-flavored markdown, not a homegrown engine. That saved me months.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Sandboxed HTML and SVG preview
&lt;/h2&gt;

&lt;p&gt;Markdown allows raw HTML, which is a footgun. Inline HTML gets sanitized. A standalone HTML file renders in a sandboxed iframe with a strict content security policy. SVG preview has no script permissions. I can preview files you drop in without giving them a way to run code against the rest of the page.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. The tiny ZIP writer behind /draw
&lt;/h2&gt;

&lt;p&gt;/draw is a screenshot annotation mode. Coordinates are stored relative to the image, so annotations survive a resize. Export is JPEG, WebP, or a ZIP of everything. Instead of adding a zip library I wrote a dependency-free STORE zip writer and ran it in a worker. No compression, which is fine for screenshots, and it stayed small.&lt;/p&gt;

&lt;p&gt;Saving is debounced IndexedDB writes with a bounded localStorage recovery copy for the case where a write dies mid-edit. PDF export is there too. The stack is React 19, TypeScript, Vite and CodeMirror 6. Built solo.&lt;/p&gt;

&lt;p&gt;The honest tradeoff: local-first is not a backup. Your docs live in one browser's storage. Clear site data and they are gone. There is no sync and no versioned history yet. I would rather say that up front.&lt;/p&gt;

&lt;p&gt;So, what is missing? If you open it with your largest markdown file, where does it break for you? What would you add first, and what would make you keep using an editor with no account?&lt;/p&gt;

</description>
      <category>markdown</category>
      <category>webdev</category>
      <category>react</category>
      <category>showdev</category>
    </item>
    <item>
      <title>why i started a tiny no-pitch group for people who ship</title>
      <dc:creator>Harshit Duggal</dc:creator>
      <pubDate>Fri, 13 Nov 2026 17:19:21 +0000</pubDate>
      <link>https://dev.to/harshitduggal/why-i-started-a-tiny-no-pitch-group-for-people-who-ship-2jc0</link>
      <guid>https://dev.to/harshitduggal/why-i-started-a-tiny-no-pitch-group-for-people-who-ship-2jc0</guid>
      <description>&lt;p&gt;every founder community i've joined ends up the same. 10k members, 5 people talking, the rest selling courses or hunting for a collab dm. the feed turns into a marketplace and the useful conversations move somewhere else.&lt;/p&gt;

&lt;p&gt;so i started a small whatsapp group for technical founders and engineers that works the other way. you post what you shipped this week and what broke. you ask the stuff you can't ask in public, like "my CAC is trash, what am i missing". you trade real numbers, tools and intros. if you have an open source repo up, you can get an actual code review instead of a reaction emoji. no pitching, no courses, no "dm for collab". if you're in, you talk, and lurkers get removed. early stage is fine.&lt;/p&gt;

&lt;p&gt;it's new and small, which is the point. a small room where people reply is worth more than a big one where nobody does. if that sounds like a group you'd actually read, join here: &lt;a href="https://chat.whatsapp.com/FNTVGrU25FsCv0sv1DPWnX" rel="noopener noreferrer"&gt;https://chat.whatsapp.com/FNTVGrU25FsCv0sv1DPWnX&lt;/a&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
