The only part of the process that&#x27;s a bit weird is loading style sheets programmatically. But I think people normally do that by adding a link tag to the DOM, so it should use browser caching as usual.<p>The other caveat is that the nature of generating common bundles automatically means that what&#x27;s in those bundles will vary whenever the code is changed. This means that you&#x27;ll lose the benefits of browser caching each time you release. If you have dependencies that you can guarantee will be in the common bundle (like it&#x27;s safe to say React will always be in it, along with any other architectural libraries), then you&#x27;re better off externalising them to somewhere that sticks around between releases (and therefore benefits more from browser caching). This will also make your common bundles much smaller.