<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Json on Paul Coding</title>
    <link>https://blog.paulcoding.com/tags/json/</link>
    <description>Recent content in Json on Paul Coding</description>
    <generator>Hugo -- 0.147.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Sep 2026 19:48:54 +0700</lastBuildDate>
    <atom:link href="https://blog.paulcoding.com/tags/json/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Decoding Nested JSON and Escaped Strings in JavaScript</title>
      <link>https://blog.paulcoding.com/posts/decode-nested-json/</link>
      <pubDate>Sun, 27 Sep 2026 16:03:00 +0700</pubDate>
      <guid>https://blog.paulcoding.com/posts/decode-nested-json/</guid>
      <description>&lt;style&gt;
  .gpt {
    font-size: 14px;
    font-style: italic;
    background: yellow;
    padding: 8px;
  }
&lt;/style&gt;

&lt;p&gt;
  &lt;span class=&#34;gpt&#34;&gt;⚠ Created by AI 🤖&lt;/span&gt;
&lt;/p&gt;

&lt;p&gt;When scraping React Server Components (RSC) data or serialized script tags from the DOM, you often encounter weirdly escaped string patterns like &lt;code&gt;push([1,&amp;quot;15:{\\\&amp;quot;@context\\\&amp;quot;:...}\\n&amp;quot;])&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Here is a quick guide on how to extract, fix the regex, and decode these nested payloads efficiently.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
