Just looking to learn here: why is it a very bad decision?
(I wasn't aware of @loadable/component when I posted this, but I've since switched my project over and have found no measurable improvement over react-loadable)
@loadable/component
react-loadable
Very bad - because it is competely unmaintained. No real answer was given to any issue, no PR has been merged.
Bad - loadable provides only a simples splitting pattern, if you don’t need SSR it’s better just to use React.lazy, it would work just the same.
Other libraries provide a better SSR support, and, for example, able to split not only components.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Just looking to learn here: why is it a very bad decision?
(I wasn't aware of
@loadable/componentwhen I posted this, but I've since switched my project over and have found no measurable improvement overreact-loadable)Very bad - because it is competely unmaintained. No real answer was given to any issue, no PR has been merged.
Bad - loadable provides only a simples splitting pattern, if you don’t need SSR it’s better just to use React.lazy, it would work just the same.
Other libraries provide a better SSR support, and, for example, able to split not only components.