Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
react-loadable compatibility component
See original GitHub issue🚀 Feature Proposal
For easier migrating from react-loadable this library can offer a Loadable HoC that wraps error handling, timeout and retries automatically. This component should conform to react-loadable API so users can easily switch to this component by simply aliasing the dependencies.
Motivation
To migrate our large repo we had to do a large refactoring change. We also lost automatic handling of timeouts and retry functionality. We had a global <Loading /> component that was consuming react-loadable props.
Pitch
This will make adopting the component framework super easy
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Maybe the complexity does not worth it. Also the API provided by React Loadable is not in the philosophy of React. For example, errors should be handled with Error Boundaries (as React.lazy), so it does not encourages good practices.
After thinking, I am not 100% against a react-loadable compat library but I will not maintain it. Feel free to create another project.
@mohsen1 Im getting the same error as @theKashey and it happens when im trying to navigate directly into a loadable route. This not happens if I navigate using the UI of my app.