From 4136300bffc11ba84e2e2d1f20254ca60155c62d Mon Sep 17 00:00:00 2001
From: Michael Hienle <40914576+mhienle@users.noreply.github.com>
Date: Tue, 1 Oct 2019 23:58:52 +0200
Subject: [PATCH] Mention Rollup (#2379)

---
 content/docs/code-splitting.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/docs/code-splitting.md b/content/docs/code-splitting.md
index c049fc49..d7ace8a2 100644
--- a/content/docs/code-splitting.md
+++ b/content/docs/code-splitting.md
@@ -63,7 +63,7 @@ it so large that your app takes a long time to load.
 To avoid winding up with a large bundle, it's good to get ahead of the problem
 and start "splitting" your bundle.
  [Code-Splitting](https://webpack.js.org/guides/code-splitting/) is a feature
-supported by bundlers like Webpack and Browserify (via
+supported by bundlers like Webpack, [Rollup](https://rollupjs.org/guide/en/#code-splitting) and Browserify (via
 [factor-bundle](https://github.com/browserify/factor-bundle)) which can create
 multiple bundles that can be dynamically loaded at runtime.