<?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>Javascript on Logan Barnett&#39;s blog</title>
    <link>https://blog.logustus.com/categories/javascript/</link>
    <description>Recent content in Javascript on Logan Barnett&#39;s blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://blog.logustus.com/categories/javascript/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title></title>
      <link>https://blog.logustus.com/demystifying-webpack/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://blog.logustus.com/demystifying-webpack/</guid>
      <description>&lt;h2 id=&#34;demystifying-webpack&#34;&gt;Demystifying Webpack&lt;/h2&gt;
&lt;div class=&#34;ox-hugo-toc toc&#34;&gt;
&lt;div class=&#34;heading&#34;&gt;Table of Contents&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;#demystifying-webpack&#34;&gt;Demystifying Webpack&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;#some-background&#34;&gt;Some Background&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#enter-webpack&#34;&gt;Enter Webpack&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#loaders&#34;&gt;Loaders&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#plugins&#34;&gt;Plugins&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#conclusion&#34;&gt;Conclusion&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;!--endtoc--&gt;
&lt;h3 id=&#34;some-background&#34;&gt;Some Background&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;ve played with a lot of the Javascript build tools in the ecosystem. Today,
&lt;a href=&#34;https://webpack.js.org&#34;&gt;Webpack&lt;/a&gt; is my go to. I like it because it adds static analysis to my file paths
for virtually everything. It also has fairly clear ways in which it transforms
files. As with any tool, there&amp;rsquo;s trade-offs to it. I can&amp;rsquo;t get map files working
for my unit tests, and the initial builds can take a really long time (upwards
of a minute). Sure I can turn some features off to speed it up, but then I&amp;rsquo;ll
miss certain errors. For example, Angular&amp;rsquo;s dependency injection system can lean
on just the function parameter names, which break when any kind of minification
is done. If I&amp;rsquo;m not minifying, I&amp;rsquo;m potentially missing those errors.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
