React.lazy() vs React Loadable

reactjs react-loadable
Roopak PutheVeettil picture Roopak PutheVeettil · Oct 29, 2018 · Viewed 10.2k times · Source

I was using react-loadable for some time for dynamic imports of my React components.

In the recent React release 16.6, the React team has included React.lazy() which also does a dynamic import.

Is there any benefit in using the react-loadable package still, or is it time to move to the new React version?

Answer

Patrick Hund picture Patrick Hund · Oct 29, 2018

No, React Loadable should not be used anymore, because it is not being maintained.

It used to be the recommended way for lazy loading when rendering on the server side, while React.lazy only works on the client side.

The React team now recommends another library for server side rendering.

Quote from the React documentation:

Note: React.lazy and Suspense is not yet available for server-side rendering. If you want to do code-splitting in a server rendered app, we still recommend Loadable Components. It has a nice guide for bundle splitting with server-side rendering.

Related questions

React-Router - Route re-rendering component on route change

Please read this properly before marking as duplicate, I assure you I've read and tried everything everyone suggests about this issue on stackoverflow and github. I have a route within my app rendered as below; <div> <Header …

Read More
Unhandled Rejection (ChunkLoadError): Loading chunk 1 failed

I am basically trying to do a poc on extracting the some part of my main application into a separate package.A Sample separate package I have built it in my git repo myapp-poc-ui. Now I am trying to access …

Read More
Can you force a React component to rerender without calling setState?

I have an external (to the component), observable object that I want to listen for changes on. When the object is updated it emits change events, and then I want to rerender the component when any change is detected. With …

Read More