react-loadable VS loadable-components

Website: https://github.com/jamiebuilds/react-loadable

React Loadable: This library makes it easy to split your React code into smaller, lazy-loaded chunks that can be loaded on demand. This can significantly improve the initial loading time of your application, especially for large and complex apps. https://github.com/jamiebuilds/react-loadable

I have a very simple React component that uses react-loadable to dynamically import another component. The code looks something akin to the following:

react-loadable - A higher order component for loading components with promises

It's very important that you are choosing an active project instead of a dead/unmaintained project. An active project improves over time through community feedback. An unmaintained project does not move forward, fix functional bugs or patch security issues. Sometimes, a very popular package can be abandoned and go into a "frozen" state with many open issues and pull requests. It might have been a great solution in the past, but this is a sign that we have to move on. An example is react-loadable. It was a great solution for a very long time for code-splitting in React. I totally loved it. But it's stale now with many issues and PRs since 2018 (this post is written at the end of 2021). Now, if I need to split code in React, I use loadable-components, which is in active development, becoming more popular, patches bugs reported by the community, and most importantly, solves my problems. My personal advice: choose a package that's active in the last 3-6 months, with issues that are being resolved and PRs that are being merged.

Preloading is possible with react-loadable: https://github.com/jamiebuilds/react-loadable#preloading

Lost of people would use the typical React method with the await import('') method, but I recommend you use a module called loadable-components.

And the best thing. It is really easy to use. Almost plug-and-play. So, give it a try! https://github.com/gregberge/loadable-components

I would like to display small loader in the component while the .svg document is loading. How can i do that? I tried to use Loadable Components - React code splitting and set fallback to the .svg component, but it doesn't work. I would like the loader to display until the entire .svg file has rendered in the DOM. What should I use to achieve this effect? In pure JavaScript, you can set the listener until the svg is rendered in the DOM.

The library @loadable/component allows you to dynamically import components to your project, so they don't get rendered on the server. The following component uses leaflet, a library similar to google maps that only supports client-side rendering:

{ "hosting": { "public": "public", "ignore": [ "firebase.json", "**/.*", "**/node_modules/**" ], "rewrites": [ { "source": "**", "function": "supercharged" } ] }} These all are the changes I made from the the loadable-components server side rendering async node example

It's very important that you are choosing an active project instead of a dead/unmaintained project. An active project improves over time through community feedback. An unmaintained project does not move forward, fix functional bugs or patch security issues. Sometimes, a very popular package can be abandoned and go into a "frozen" state with many open issues and pull requests. It might have been a great solution in the past, but this is a sign that we have to move on. An example is react-loadable. It was a great solution for a very long time for code-splitting in React. I totally loved it. But it's stale now with many issues and PRs since 2018 (this post is written at the end of 2021). Now, if I need to split code in React, I use loadable-components, which is in active development, becoming more popular, patches bugs reported by the community, and most importantly, solves my problems. My personal advice: choose a package that's active in the last 3-6 months, with issues that are being resolved and PRs that are being merged.

Now client side rendering is very powerful and as I said in the first comment I'm two years in production of an app that's using things like lazy loading and client side routing and more to give the app a more regular application feel, but by using next.js to generate a static site my users would have benefited by not having to generate all the javascript their using on their own pcs.

When we have lot of pages in out application, we will end up having lot of code. We don't want our user to download all the code when they just load the home page. In order to package code of different routes to separate chunks, along with react router we can make use of loadable components, which takes advantage of dynamic imports.

// Components.js export const Component = /* ... */; export const UnusedComponent = /* ... */; // Component.js export { Component as default } from "./Components.js"; As both React.lazy and Suspense are not available for rendering on the server yet now, it is recommended to use https://github.com/gregberge/loadable-components for code-splitting in a server-rendered app (SSR). React.lazy is helpful for rendering dynamic import as a regular component in client-rendered app (CSR). Magic Comment at import() import( /* webpackChunkName: "test", webpackPrefetch: true */ "LoginModal" ) // or import( /* webpackChunkName: "test" */ /* webpackPrefetch: true */ "LoginModal" ) // spacing optional "webpackChunkName" : Using this magic comment we can set name for the js chunk that is loaded on demand.

In order to load the CatImage component to a separate bundle, we can make use of loadable components. Let's add @loadable-component to our package: