The ability to reply to discussions is limited to PRO members. Want to join in the discussion? Click here to subscribe now.

Maintain sane file sizes with webpack code splitting

Maintain sane file sizes with webpack code splitting

2:38
As a Single Page Application grows in size, the size of the payload can become a real problem for performance. In this lesson, learn how to leverage code splitting to easily implement lazy loading for your application to load only the code necessary for a particular feature or functionality.
Watch this lesson now
Avatar
egghead.io

As a Single Page Application grows in size, the size of the payload can become a real problem for performance. In this lesson, learn how to leverage code splitting to easily implement lazy loading for your application to load only the code necessary for a particular feature or functionality.

Avatar
Peng

What is the editor's name that you are using in this video?

Avatar
Kent C.

It's called Atom. Here are the plugins I use: https://github.com/kentcdodds/ama/issues/113

In reply to Peng
Avatar
Dan Hayden

When using System.import webpack creates the correct bundles however when it attempts to load the bundle in the browser it tries to load it from the root directory and not the webpack output directory.
Has anyone else had this problem or know how to fix it?
Thanks

Avatar
Kent C.

You probably need to set the output.publicPath.

In reply to Dan Hayden
Avatar
Dan Hayden

That worked! Thank you so much Kent 👍

In reply to Kent C.
Avatar
Andrejb

Thank you very much for this highly professional lessons! Your explanations are best on the planet, happy to extend the skills by this!

Avatar
Kent C.

That's super nice of you to say! Thank you! I'm glad it's helpful!

In reply to Andrejb
HEY, QUICK QUESTION!
Joel's Head
Why are we asking?