# Code Splitting with Webpack and Aurelia for Lazy Loading

**URL:** <https://discourse.aurelia.io/t/code-splitting-with-webpack-and-aurelia-for-lazy-loading/197>\
**Category:** Best Practices\
**Created:** [October 26, 2017, 4:16pm UTC](https://discourse.aurelia.io/t/code-splitting-with-webpack-and-aurelia-for-lazy-loading/197 "2017-10-26T16:16:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rkever](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/rkever/32/145_2.png) [@rkever](https://discourse.aurelia.io/u/rkever)\
**Post date:** [October 26, 2017, 4:16pm UTC](https://discourse.aurelia.io/t/code-splitting-with-webpack-and-aurelia-for-lazy-loading/197/1 "2017-10-26T16:16:13Z")

</div>

Just wanted to reference this great article about one way to “code split” your app for larger applications and lazy loading modules when needed. It’s working well for us and for sure has reduced the apps load time and size. Just a note on what happens when you do use it in the route, I’ve verified that it not only splits out the view/viewmodel from the route moduleId but also other child components too that aren’t already loaded in the app.bundles.js.

> **[Code Splitting Your Aurelia Webpack Applications - I Like Kill Nerds](https://ilikekillnerds.com/2017/03/code-splitting-aurelia-webpack-applications/)**
>
> In this article we won’t be detailing how to setup a new Webpack application, but how you can leverage code splitting to reduce the size of your application. If you would like to know how to create a new Webpack application capable of supporting code...