<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>web01.fireside.fm</fireside:hostname>
    <fireside:genDate>Wed, 20 May 2026 05:29:17 -0500</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>PodRocket - Episodes Tagged with “Source Maps”</title>
    <link>https://podrocket.logrocket.com/tags/source%20maps</link>
    <pubDate>Tue, 21 Oct 2025 08:00:00 -0400</pubDate>
    <description>PodRocket covers everything you need to know about frontend web development on a weekly basis. Join our hosts as they interview experienced developers about all the libraries, frameworks, and tech industry issues they deal with every day.
</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>A web development podcast from LogRocket</itunes:subtitle>
    <itunes:author>LogRocket</itunes:author>
    <itunes:summary>PodRocket covers everything you need to know about frontend web development on a weekly basis. Join our hosts as they interview experienced developers about all the libraries, frameworks, and tech industry issues they deal with every day.
</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/3/3911462c-bca2-48c2-9103-610ba304c673/cover.jpg?v=4"/>
    <itunes:explicit>no</itunes:explicit>
    <itunes:keywords>front-end, web development, front-end development, frontend development, tech, </itunes:keywords>
    <itunes:owner>
      <itunes:name>LogRocket</itunes:name>
      <itunes:email>elizabeth.becz@logrocket.com</itunes:email>
    </itunes:owner>
<itunes:category text="Technology"/>
<item>
  <title>Source maps: how does the magic work? with Nicolo Ribaudo</title>
  <link>http://podrocket.logrocket.com/source-maps-nicolo-ribaudo</link>
  <guid isPermaLink="false">f5b5a2e3-8ab0-422c-a96a-6c083c0e48c4</guid>
  <pubDate>Tue, 21 Oct 2025 08:00:00 -0400</pubDate>
  <author>LogRocket</author>
  <enclosure url="https://dts.podtrac.com/redirect.mp3/aphid.fireside.fm/d/1437767933/3911462c-bca2-48c2-9103-610ba304c673/f5b5a2e3-8ab0-422c-a96a-6c083c0e48c4.mp3" length="62056448" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>LogRocket</itunes:author>
  <itunes:subtitle>Ever wondered how source maps actually work? In this episode, Nicolo Ribaudo, Babel maintainer and TC39 delegate, breaks down how source maps connect your JavaScript, TypeScript, and CSS back to the original code — making debugging, stack traces, and observability smoother in Chrome dev tools.

We dive into how source maps help in both development and production with minified code, explore tools like Webpack, Rollup, Next.js, and Svelte, and share when you should turn off source maps to avoid confusion.</itunes:subtitle>
  <itunes:duration>25:51</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/3/3911462c-bca2-48c2-9103-610ba304c673/episodes/f/f5b5a2e3-8ab0-422c-a96a-6c083c0e48c4/cover.jpg?v=1"/>
  <description>&lt;p&gt;Ever wondered how source maps actually work? In this episode, Nicolo Ribaudo, Babel maintainer and TC39 delegate, breaks down how source maps connect your JavaScript, TypeScript, and CSS back to the original code — making debugging, stack traces, and observability smoother in Chrome dev tools.&lt;/p&gt;

&lt;p&gt;We dive into how source maps help in both development and production with minified code, explore tools like Webpack, Rollup, Next.js, and Svelte, and share when you should turn off source maps to avoid confusion.&lt;/p&gt;

&lt;h3&gt;Links&lt;/h3&gt;

&lt;p&gt;Website: &lt;a href="https://nicr.dev" target="_blank" rel="nofollow noopener"&gt;https://nicr.dev&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/nicol%C3%B2-ribaudo-bb94b4187" target="_blank" rel="nofollow noopener"&gt;https://www.linkedin.com/in/nicol%C3%B2-ribaudo-bb94b4187&lt;/a&gt;&lt;br&gt;
BlueSky: &lt;a href="https://bsky.app/profile/nicr.dev" target="_blank" rel="nofollow noopener"&gt;https://bsky.app/profile/nicr.dev&lt;/a&gt;&lt;br&gt;
Github: &lt;a href="https://github.com/nicolo-ribaudo" target="_blank" rel="nofollow noopener"&gt;https://github.com/nicolo-ribaudo&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;Resources&lt;/h3&gt;

&lt;p&gt;Squiggleconf talk: &lt;a href="https://squiggleconf.com/2025/sessions#source-maps-how-does-the-magic-work" target="_blank" rel="nofollow noopener"&gt;https://squiggleconf.com/2025/sessions#source-maps-how-does-the-magic-work&lt;/a&gt;&lt;br&gt;
Slide deck: &lt;a href="https://docs.google.com/presentation/d/1lyor5xgv821I4kUWJIwrrmXBjzC_qiqIqcZxve1ybw0" target="_blank" rel="nofollow noopener"&gt;https://docs.google.com/presentation/d/1lyor5xgv821I4kUWJIwrrmXBjzC_qiqIqcZxve1ybw0&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;We want to hear from you!&lt;/h3&gt;

&lt;p&gt;How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fill out our &lt;a href="https://t.co/oKVAEXipxu" target="_blank" rel="nofollow noopener"&gt;listener survey&lt;/a&gt;!&lt;/strong&gt; &lt;a href="https://t.co/oKVAEXipxu" target="_blank" rel="nofollow noopener"&gt;https://t.co/oKVAEXipxu&lt;/a&gt;&lt;br&gt;
Let us know by sending an email to our producer, Elizabeth, at &lt;a href="mailto:elizabeth.becz@logrocket.com" target="_blank" rel="nofollow noopener"&gt;elizabet.becz@logrocket.com&lt;/a&gt;, or tweet at us at &lt;a href="https://twitter.com/PodRocketpod" target="_blank" rel="nofollow noopener"&gt;PodRocketPod&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check out our &lt;a href="https://blog.logrocket.com/the-replay-newsletter/" target="_blank" rel="nofollow noopener"&gt;newsletter&lt;/a&gt;!&lt;/strong&gt; &lt;a href="https://blog.logrocket.com/the-replay-newsletter/" target="_blank" rel="nofollow noopener"&gt;https://blog.logrocket.com/the-replay-newsletter/&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;Follow us. Get free stickers.&lt;/h3&gt;

&lt;p&gt;Follow us on Apple Podcasts, fill out this &lt;a href="https://podrocket.logrocket.com/get-podrocket-stickers" target="_blank" rel="nofollow noopener"&gt;form&lt;/a&gt;, and we’ll send you free PodRocket stickers!&lt;/p&gt;

&lt;h3&gt;What does LogRocket do?&lt;/h3&gt;

&lt;p&gt;LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. &lt;a href="https://logrocket.com/signup/?pdr" target="_blank" rel="nofollow noopener"&gt;Try LogRocket for free today.&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;Chapters&lt;/h3&gt;

&lt;p&gt;00:00 Intro – Welcome to PodRocket + Introducing Nicolo Ribaudo&lt;br&gt;
00:45 What Are Source Maps and Why They Matter for Debugging&lt;br&gt;
01:20 From Babel to TC39 – Nicolo’s Path to Source Maps&lt;br&gt;
02:00 Source Maps Beyond JavaScript: CSS, C, and WebAssembly&lt;br&gt;
03:00 The Core Idea – Mapping Compiled Code Back to Source&lt;br&gt;
04:00 How Source Maps Work Under the Hood (Encoded JSON)&lt;br&gt;
05:10 File Size and Performance – Why It Doesn’t Matter in Production&lt;br&gt;
06:00 Why Source Maps Are Useful Even Without Minification&lt;br&gt;
07:00 Sentry and Error Monitoring – How Source Maps Are Used in Production&lt;br&gt;
08:10 Two Worlds: Local Debugging vs. Remote Error Analysis&lt;br&gt;
09:00 You’re Probably Using Source Maps Without Realizing It&lt;br&gt;
10:00 Why Standardization Was Needed After 15+ Years of Chaos&lt;br&gt;
11:00 TC39 and the Creation of the Official Source Maps Standard&lt;br&gt;
12:00 Coordinating Browsers, Tools, and Vendors Under One Spec&lt;br&gt;
13:00 How Chrome, Firefox, and WebKit Implement Source Maps Differently&lt;br&gt;
14:00 Why the Source Maps Working Group Moves Faster Than Other Standards&lt;br&gt;
15:00 A Small, Focused Group of DevTools Engineers&lt;br&gt;
16:00 How Build Tools and Bundlers Feed Into the Ecosystem&lt;br&gt;
17:00 Making It Easier for Tool Authors to Generate Source Maps&lt;br&gt;
18:00 How Frameworks Like Next.js and Vite Handle Source Maps for You&lt;br&gt;
19:00 Common Pitfalls When Chaining Build Tools&lt;br&gt;
20:00 Debugging Wrong or Broken Source Maps in Browsers&lt;br&gt;
21:00 Upcoming Feature: Scopes for Variables and Functions&lt;br&gt;
22:00 How Scopes Improve the Live Debugging Experience&lt;br&gt;
23:00 Experimental Implementations and How to Try Them&lt;br&gt;
24:00 Where to Find the TC39 Source Maps Group + Get Involved&lt;br&gt;
25:00 Nicolo’s Links – GitHub, BlueSky, and Talks Online&lt;br&gt;
25:30 Closing Thoughts &lt;/p&gt;
</description>
  <itunes:keywords>source maps, Nicolo Ribaudo, Babel, TC 39, JavaScript, TypeScript, CSS, Post CSS, Less, SaaS, C to Wasm compiler, Chrome dev tools, observability, debugging, break point, minified code, production, development, stack traces, Century, web pack, Webpac, roll up, next js, spelt, turn off source maps, scopes, TC 39 Source Maps GitHub, Blue Sky, GitHub, standardization</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>Ever wondered how source maps actually work? In this episode, Nicolo Ribaudo, Babel maintainer and TC39 delegate, breaks down how source maps connect your JavaScript, TypeScript, and CSS back to the original code — making debugging, stack traces, and observability smoother in Chrome dev tools.</p>

<p>We dive into how source maps help in both development and production with minified code, explore tools like Webpack, Rollup, Next.js, and Svelte, and share when you should turn off source maps to avoid confusion.</p>

<h3>Links</h3>

<p>Website: <a href="https://nicr.dev" rel="nofollow">https://nicr.dev</a><br>
LinkedIn: <a href="https://www.linkedin.com/in/nicol%C3%B2-ribaudo-bb94b4187" rel="nofollow">https://www.linkedin.com/in/nicol%C3%B2-ribaudo-bb94b4187</a><br>
BlueSky: <a href="https://bsky.app/profile/nicr.dev" rel="nofollow">https://bsky.app/profile/nicr.dev</a><br>
Github: <a href="https://github.com/nicolo-ribaudo" rel="nofollow">https://github.com/nicolo-ribaudo</a></p>

<h3>Resources</h3>

<p>Squiggleconf talk: <a href="https://squiggleconf.com/2025/sessions#source-maps-how-does-the-magic-work" rel="nofollow">https://squiggleconf.com/2025/sessions#source-maps-how-does-the-magic-work</a><br>
Slide deck: <a href="https://docs.google.com/presentation/d/1lyor5xgv821I4kUWJIwrrmXBjzC_qiqIqcZxve1ybw0" rel="nofollow">https://docs.google.com/presentation/d/1lyor5xgv821I4kUWJIwrrmXBjzC_qiqIqcZxve1ybw0</a></p>

<h3>We want to hear from you!</h3>

<p>How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend?</p>

<p><strong>Fill out our <a href="https://t.co/oKVAEXipxu" rel="nofollow">listener survey</a>!</strong> <a href="https://t.co/oKVAEXipxu" rel="nofollow">https://t.co/oKVAEXipxu</a><br>
Let us know by sending an email to our producer, Elizabeth, at <a href="mailto:elizabeth.becz@logrocket.com" rel="nofollow">elizabet.becz@logrocket.com</a>, or tweet at us at <a href="https://twitter.com/PodRocketpod" rel="nofollow">PodRocketPod</a>.</p>

<p><strong>Check out our <a href="https://blog.logrocket.com/the-replay-newsletter/" rel="nofollow">newsletter</a>!</strong> <a href="https://blog.logrocket.com/the-replay-newsletter/" rel="nofollow">https://blog.logrocket.com/the-replay-newsletter/</a></p>

<h3>Follow us. Get free stickers.</h3>

<p>Follow us on Apple Podcasts, fill out this <a href="https://podrocket.logrocket.com/get-podrocket-stickers" rel="nofollow">form</a>, and we’ll send you free PodRocket stickers!</p>

<h3>What does LogRocket do?</h3>

<p>LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. <a href="https://logrocket.com/signup/?pdr" rel="nofollow">Try LogRocket for free today.</a></p>

<h3>Chapters</h3>

<p>00:00 Intro – Welcome to PodRocket + Introducing Nicolo Ribaudo<br>
00:45 What Are Source Maps and Why They Matter for Debugging<br>
01:20 From Babel to TC39 – Nicolo’s Path to Source Maps<br>
02:00 Source Maps Beyond JavaScript: CSS, C, and WebAssembly<br>
03:00 The Core Idea – Mapping Compiled Code Back to Source<br>
04:00 How Source Maps Work Under the Hood (Encoded JSON)<br>
05:10 File Size and Performance – Why It Doesn’t Matter in Production<br>
06:00 Why Source Maps Are Useful Even Without Minification<br>
07:00 Sentry and Error Monitoring – How Source Maps Are Used in Production<br>
08:10 Two Worlds: Local Debugging vs. Remote Error Analysis<br>
09:00 You’re Probably Using Source Maps Without Realizing It<br>
10:00 Why Standardization Was Needed After 15+ Years of Chaos<br>
11:00 TC39 and the Creation of the Official Source Maps Standard<br>
12:00 Coordinating Browsers, Tools, and Vendors Under One Spec<br>
13:00 How Chrome, Firefox, and WebKit Implement Source Maps Differently<br>
14:00 Why the Source Maps Working Group Moves Faster Than Other Standards<br>
15:00 A Small, Focused Group of DevTools Engineers<br>
16:00 How Build Tools and Bundlers Feed Into the Ecosystem<br>
17:00 Making It Easier for Tool Authors to Generate Source Maps<br>
18:00 How Frameworks Like Next.js and Vite Handle Source Maps for You<br>
19:00 Common Pitfalls When Chaining Build Tools<br>
20:00 Debugging Wrong or Broken Source Maps in Browsers<br>
21:00 Upcoming Feature: Scopes for Variables and Functions<br>
22:00 How Scopes Improve the Live Debugging Experience<br>
23:00 Experimental Implementations and How to Try Them<br>
24:00 Where to Find the TC39 Source Maps Group + Get Involved<br>
25:00 Nicolo’s Links – GitHub, BlueSky, and Talks Online<br>
25:30 Closing Thoughts</p>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>Ever wondered how source maps actually work? In this episode, Nicolo Ribaudo, Babel maintainer and TC39 delegate, breaks down how source maps connect your JavaScript, TypeScript, and CSS back to the original code — making debugging, stack traces, and observability smoother in Chrome dev tools.</p>

<p>We dive into how source maps help in both development and production with minified code, explore tools like Webpack, Rollup, Next.js, and Svelte, and share when you should turn off source maps to avoid confusion.</p>

<h3>Links</h3>

<p>Website: <a href="https://nicr.dev" rel="nofollow">https://nicr.dev</a><br>
LinkedIn: <a href="https://www.linkedin.com/in/nicol%C3%B2-ribaudo-bb94b4187" rel="nofollow">https://www.linkedin.com/in/nicol%C3%B2-ribaudo-bb94b4187</a><br>
BlueSky: <a href="https://bsky.app/profile/nicr.dev" rel="nofollow">https://bsky.app/profile/nicr.dev</a><br>
Github: <a href="https://github.com/nicolo-ribaudo" rel="nofollow">https://github.com/nicolo-ribaudo</a></p>

<h3>Resources</h3>

<p>Squiggleconf talk: <a href="https://squiggleconf.com/2025/sessions#source-maps-how-does-the-magic-work" rel="nofollow">https://squiggleconf.com/2025/sessions#source-maps-how-does-the-magic-work</a><br>
Slide deck: <a href="https://docs.google.com/presentation/d/1lyor5xgv821I4kUWJIwrrmXBjzC_qiqIqcZxve1ybw0" rel="nofollow">https://docs.google.com/presentation/d/1lyor5xgv821I4kUWJIwrrmXBjzC_qiqIqcZxve1ybw0</a></p>

<h3>We want to hear from you!</h3>

<p>How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend?</p>

<p><strong>Fill out our <a href="https://t.co/oKVAEXipxu" rel="nofollow">listener survey</a>!</strong> <a href="https://t.co/oKVAEXipxu" rel="nofollow">https://t.co/oKVAEXipxu</a><br>
Let us know by sending an email to our producer, Elizabeth, at <a href="mailto:elizabeth.becz@logrocket.com" rel="nofollow">elizabet.becz@logrocket.com</a>, or tweet at us at <a href="https://twitter.com/PodRocketpod" rel="nofollow">PodRocketPod</a>.</p>

<p><strong>Check out our <a href="https://blog.logrocket.com/the-replay-newsletter/" rel="nofollow">newsletter</a>!</strong> <a href="https://blog.logrocket.com/the-replay-newsletter/" rel="nofollow">https://blog.logrocket.com/the-replay-newsletter/</a></p>

<h3>Follow us. Get free stickers.</h3>

<p>Follow us on Apple Podcasts, fill out this <a href="https://podrocket.logrocket.com/get-podrocket-stickers" rel="nofollow">form</a>, and we’ll send you free PodRocket stickers!</p>

<h3>What does LogRocket do?</h3>

<p>LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. <a href="https://logrocket.com/signup/?pdr" rel="nofollow">Try LogRocket for free today.</a></p>

<h3>Chapters</h3>

<p>00:00 Intro – Welcome to PodRocket + Introducing Nicolo Ribaudo<br>
00:45 What Are Source Maps and Why They Matter for Debugging<br>
01:20 From Babel to TC39 – Nicolo’s Path to Source Maps<br>
02:00 Source Maps Beyond JavaScript: CSS, C, and WebAssembly<br>
03:00 The Core Idea – Mapping Compiled Code Back to Source<br>
04:00 How Source Maps Work Under the Hood (Encoded JSON)<br>
05:10 File Size and Performance – Why It Doesn’t Matter in Production<br>
06:00 Why Source Maps Are Useful Even Without Minification<br>
07:00 Sentry and Error Monitoring – How Source Maps Are Used in Production<br>
08:10 Two Worlds: Local Debugging vs. Remote Error Analysis<br>
09:00 You’re Probably Using Source Maps Without Realizing It<br>
10:00 Why Standardization Was Needed After 15+ Years of Chaos<br>
11:00 TC39 and the Creation of the Official Source Maps Standard<br>
12:00 Coordinating Browsers, Tools, and Vendors Under One Spec<br>
13:00 How Chrome, Firefox, and WebKit Implement Source Maps Differently<br>
14:00 Why the Source Maps Working Group Moves Faster Than Other Standards<br>
15:00 A Small, Focused Group of DevTools Engineers<br>
16:00 How Build Tools and Bundlers Feed Into the Ecosystem<br>
17:00 Making It Easier for Tool Authors to Generate Source Maps<br>
18:00 How Frameworks Like Next.js and Vite Handle Source Maps for You<br>
19:00 Common Pitfalls When Chaining Build Tools<br>
20:00 Debugging Wrong or Broken Source Maps in Browsers<br>
21:00 Upcoming Feature: Scopes for Variables and Functions<br>
22:00 How Scopes Improve the Live Debugging Experience<br>
23:00 Experimental Implementations and How to Try Them<br>
24:00 Where to Find the TC39 Source Maps Group + Get Involved<br>
25:00 Nicolo’s Links – GitHub, BlueSky, and Talks Online<br>
25:30 Closing Thoughts</p>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
