<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Webpack5 on CSP Guide</title>
    <link>https://csp-guide.com/tags/webpack5/</link>
    <description>Recent content in Webpack5 on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/webpack5/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Handle CSP with Webpack 5</title>
      <link>https://csp-guide.com/posts/how-to-handle-csp-with-webpack-5/</link>
      <pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/how-to-handle-csp-with-webpack-5/</guid>
      
      <description>&lt;p&gt;Content Security Policy and Webpack 5 have a slightly annoying relationship.&lt;/p&gt;
&lt;p&gt;Webpack wants to inject runtime code, lazy-load chunks, and smooth over browser differences. CSP wants you to be explicit about every script, style, and connection. If you just turn on a strict policy after shipping a typical Webpack app, something usually breaks.&lt;/p&gt;
&lt;p&gt;The good news: Webpack 5 works fine with CSP if you wire it up deliberately.&lt;/p&gt;
&lt;p&gt;This guide is the version I wish I had the first time I locked down a production bundle.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
