<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Webpack on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/webpack/</link><description>Recent content in Webpack on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 05 Jul 2018 17:15:28 +0000</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/webpack/index.xml" rel="self" type="application/rss+xml"/><item><title>Intro to Webpack</title><link>https://blog.sodawa.com/blog/intro-to-webpack-4/</link><pubDate>Thu, 05 Jul 2018 17:15:28 +0000</pubDate><guid>https://blog.sodawa.com/blog/intro-to-webpack-4/</guid><description>Alot of Webpack introdutions focus on how to set up your first webpack configuration.
What I want to do in this article is taking a step back and look at what webpack is actually doing before going into the setup and all its complications.
The problem In the frontend we have a variety of targets that we want our applications to run in, and they are all browsers. Some old, some new.</description></item><item><title>AB testing bundles with webpack</title><link>https://blog.sodawa.com/blog/ab-testing-bundles-with-webpack/</link><pubDate>Tue, 03 Oct 2017 16:43:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/ab-testing-bundles-with-webpack/</guid><description>In this post I want to show you a quick way to get some basic AB testing functionality in place via a webpack loader.
All code can be found at my github repo.
The basic page Lets say we have the following page running in production:
Unfortunately the picture that was here has been lost into the void
The App component looks like this
import React from 'react'; import Button from '.</description></item></channel></rss>