react-router VS react-loadable

React Router

React Router: This library provides routing capabilities for React applications. It offers a simple and flexible API, with features like lazy loading, dynamic routes, and support for mobile devices. https://github.com/ReactTraining/react-router

I'm using react-router-redux (https://github.com/ReactTraining/react-router/tree/master/packages/react-router-redux)

While searching for a solution I found https://github.com/ReactTraining/react-router/issues/5801related to my problem, but no solution.

However, it seems that react router is the overwhelmingly dominant browsing solution for react + redux apps. react-router has 28,355 stars on github to redux-first-routing's 76. This double source of truth issue seems like a common one. Why has redux first routing not seen wider adoption? How do people solve this problem with react router? Why is react router worth the inconvenience of connecting your components to both the router and redux state?

// Exerp From: https://github.com/ReactTraining/react-router/issues/4105export const renderMergedProps = (component, ...rest) => { const finalProps = Object.assign({}, ...rest); return ( React.createElement(component, finalProps) );}export const PropsRoute = ({ component, ...rest }) => { return ( { return renderMergedProps(component, routeProps, rest); }}/> );} Most of the documentation and articles online are for v2&3. The docs for v4 don't go into detail on how to handle this. Many people nested a route for their app. However, when I do that, I get a stack overflow in the console with a print of the frames.

I have read this document about react-router Switch

One point of significance here is this from @TrevorRobinson's answer "the browser's automatic attempts at scroll restoration... ...mostly don't work for single-page apps..." Ok... I found consistent support for history.scrollRestoration, but apparently browsers are crappy at actually DOING the scroll restoration. Then that should be noted here, which would have saved me time today.

I know this is a loaded question, but I want to effectively use these 3 libs(React-Router V4, Redux-persist, React-snapshot) together to serve protected routes without the mentioned errors.

http://example.com/robots.txt I see on this page that:

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