<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>React on JsonKit Blog</title>
    <link>https://jsokit.com/blog/tags/react/</link>
    <description>Recent content in React on JsonKit Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2025 JsonKit</copyright>
    <lastBuildDate>Mon, 16 Mar 2026 20:07:38 +0000</lastBuildDate>
    <atom:link href="https://jsokit.com/blog/tags/react/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux df Command Deep Dive: From Disk Space Monitoring to inode Exhaustion Troubleshooting</title>
      <link>https://jsokit.com/blog/posts/linux-df-command-deep-dive-from-disk-space-monitoring-to-inode-exhaustion-troubleshooting/</link>
      <pubDate>Mon, 16 Mar 2026 20:07:38 +0000</pubDate>
      <guid>https://jsokit.com/blog/posts/linux-df-command-deep-dive-from-disk-space-monitoring-to-inode-exhaustion-troubleshooting/</guid>
      <description>Linux df Command Deep Dive: From Disk Space Monitoring to inode Exhaustion Troubleshooting Server disk full, SSH login fails with No space left on device. First reaction: df -h. But sometimes there&amp;rsquo;s still space showing, yet errors persist—that&amp;rsquo;s inode exhaustion. After diving deep into the df command, I found this seemingly simple tool hides quite a few intricacies.&#xA;df&amp;rsquo;s Underlying Implementation: statvfs System Call The core data of df comes from the statvfs() system call, which returns filesystem statistics:</description>
    </item>
    <item>
      <title>JSON Tree Editor: Recursive Rendering and Two-Way Sync</title>
      <link>https://jsokit.com/blog/posts/json-tree-editor-recursive-rendering-and-two-way-sync/</link>
      <pubDate>Mon, 09 Mar 2026 17:57:52 +0000</pubDate>
      <guid>https://jsokit.com/blog/posts/json-tree-editor-recursive-rendering-and-two-way-sync/</guid>
      <description>JSON Tree Editor: Recursive Rendering and Two-Way Sync Working with complex JSON data recently, plain text editing wasn&amp;rsquo;t cutting it. I needed a visual tree editor where I could add, delete, and modify nodes directly. So I built one. Here&amp;rsquo;s the core approach.&#xA;Data Model for Tree Structure Converting JSON to a tree requires a unified node model:&#xA;interface TreeNode { id: string // Unique identifier (React key + node lookup) key: string // Key name value: any // Value (primitive stored directly, object/array as reference) type: &amp;#39;object&amp;#39; | &amp;#39;array&amp;#39; | &amp;#39;string&amp;#39; | &amp;#39;number&amp;#39; | &amp;#39;boolean&amp;#39; | &amp;#39;null&amp;#39; children?</description>
    </item>
    <item>
      <title>Building an Icon Library Tool: From Lucide React to Search Filtering</title>
      <link>https://jsokit.com/blog/posts/building-an-icon-library-tool-from-lucide-react-to-search-filtering/</link>
      <pubDate>Thu, 19 Feb 2026 11:31:12 +0000</pubDate>
      <guid>https://jsokit.com/blog/posts/building-an-icon-library-tool-from-lucide-react-to-search-filtering/</guid>
      <description>Building an Icon Library Tool: From Lucide React to Search Filtering Managing icons in frontend projects is always a hassle. Designers send a bunch of SVGs, developers manually import, name, and wrap them. Recently discovered Lucide React, a clean icon library with simple API and high-quality icons. Built an online icon library tool and documented the implementation approach.&#xA;Lucide React&amp;rsquo;s Design Philosophy Lucide is a community-maintained fork of Feather Icons with consistent style and clean lines.</description>
    </item>
  </channel>
</rss>
