In the real world, things often break, right?
It’s possible that in the process of fetching the lazy-loaded resource, a network error occurs.
To handle such a case, be sure to wrap your lazy-loaded components in an error boundary.
Remember error boundaries from the Lifecycle methods chapter?
Here’s an example: