Let's consider a React app with multiple routes: a landing page route, another one to get a list of todos, another one to inspect todos. Each route renders a specific view / components. We carefully read the React documentation about code splitting and used React.Lazy and React.Suspense which results in us having a codebase similar to the following:

1
import React from 'React';
2
import { Route, Router, Switch } from 'react-router-dom';
4
const App = React.lazy(() => import('./App'));
5
const Todos = React.lazy(() => import('./Todos'));
6
const Todo = React.lazy(() => import('./Todo'));
9
  { path: '/', exact: true, component: App },
10
  { path: '/todos', exact: true, component: Todos },
11
  { path: '/todos/:id', exact: true, component: Todo },
16
    <React.Suspense fallback={'Loading'}>
18
        {routes.map((route) => (
23
            component={route.component}

If we run our app, we can see in the developer tools of our browser that navigating from one view to another is loading the different "pieces" or "chunks" of our app. Now let's focus on how we could start loading these chunks when the user hovers one of the navigation links instead of loading them after navigating to the new route.

To preload the view we'll have to be able to call a preload method on our chunk. This preload method would be able to be called to run the import statement that is passed to React Lazy. While such functionality is available out of the box in React Loadable, React Lazy doesn't seem to provide it and this is why we'll have to implement it from scratch with the following code:

1
const ReactLazyPreload = (importStatement) => {
2
  const Component = React.lazy(importStatement);
3
  Component.preload = importStatement;

We can now redeclare our code split chunks as follows:

1
const App = ReactLazyPreload(() => import('./App'));
3
const Todos = ReactLazyPreload(() => import('./Todos'));
5
const Todo = ReactLazyPreload(() => import('./Todo'));

With the code above we can now call the preload method at will on any of our components which will result in each of them loading their respective chunks:

While we could specify which component we'd wish to preload when the user hovers a given link, wouldn't it be great if we could "find" which component to preload based on the route? If we take a look at the first code snippet of this post, we can see that we declared a routes object that contains all the properties required by the React Router Route component. This is intentional and will be useful for us to find which component is associated to which route.

Let's declare our findComponentForRoute function:

1
import { matchPath } from 'react-router-dom';
3
const findComponentForRoute = (path, routes) => {
4
  const matchingRoute = routes.find((route) =>
11
  return matchingRoute ? matchingRoute.component : null;

React Router comes with a pretty handy method called matchPath which for a given path will return true if the path passed in the second argument matches. The function in the code snippet above uses this method and when a match is found, returns the associated component or null if no route has been found.

Now that we have a way to find the component associalted to a given route, we can create a function to preload it:

1
const preloadRouteComponent = (path) => {
2
  const component = findComponentForRoute(path, routes);
4
  if (component && component.preload) {

Finally, we could just add this function to a onMouseEnter event handler to all our Link components and call it a day but let's make the things we just implemented easier to use. Let's create a LinkWithPreload component that will have the same props as Link but will also use the preloadRouteComponent function:

1
import { Link } from 'react-router-dom'
5
const LinkWithPreload = ({ to, onPreload, ...rest }) => {
9
      onMouseEnter={() => preloadRouteComponent(to)}
15
export default LinkWithPreload;

Now, by using this component instead of Link, as you can see below, hovering any navigational links in our App should load the chunk associated with the route of that link:

Do you want to see the whole code? I made the app showcased in this article available here!