-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relay 9 #155
Relay 9 #155
Conversation
I'm hesitant about switching to
^^ sounds like they now officially maintain the project but I didn't find any confirmation. Based on this comment it seems they just decided to copy the project without even properly forking and merge in the change. There were no changes since the fork was create and don't have any certainty "this community fork" will be better maintained. |
Actually, they do credit the original project, see https://github.com/yeutech-lab/react-loadable#why-did-we-fork |
Its a community fork, they fixed the bugs and left it, I don't see why not updating the list of users is so bad. They made the changes needed, and left it. |
Here are my concerns about using this "fork":
|
Signed-off-by: Reece Dunham <[email protected]>
Fixed |
Regarding the react-loadable. It seems https://github.com/gregberge/loadable-components worth investigation. |
https://www.npmjs.com/package/react-loadable-hooks implementation with React 17 |
@velusgautam ended up switching to React's lazy right after is #159 |
Signed-off-by: Reece Dunham [email protected]
New in this PR 🔥
Feature 🖥
Dependencies ⛽️
@material-ui/core
Bug Fixes 🐞