Skip to content
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

Comparison with other libraries #2

Closed
oyeanuj opened this issue Jun 24, 2017 · 6 comments
Closed

Comparison with other libraries #2

oyeanuj opened this issue Jun 24, 2017 · 6 comments

Comments

@oyeanuj
Copy link

oyeanuj commented Jun 24, 2017

Hi @neoziro @vvo! This library looks great - thank you for open sourcing this!

Its probably on your list, but if not, do consider providing a more indepth comparison with react-loadable, and react-async-components.

Personally, I am curious to understand if SSR is the main difference, or are there other differences, as well, as how you approach SSR differently from those libraries.

It'd be super helpful to folks, like me, trying to pick a library!

Thank you!

@gregberge
Copy link
Owner

@oyeanuj thank you!

I tried to explain it in the readme.

I also documented how to implement a delay and how to implement a timeout.

@dickenwong
Copy link

@neoziro I saw this in the documentation.

react-loadable was the recommended way for React code splitting for a long time. However, today it is not maintained any more and it is not compatible with Webpack v4+ and Babel v7+.

I'm confused because I see commits on react-loadable, and it runs perfectly with webpack v4.
Except it is not real "open source", I'm curious to see currently any main difference from that library?

Thank you!

@theKashey
Copy link
Collaborator

"Commits"
screen shot 2018-12-17 at 3 52 09 pm

@theKashey
Copy link
Collaborator

Better - compare this react-loadable fork, with react-loadable. That's the answer.

@gregberge
Copy link
Owner

Since september, just a readme commit. Issues disabled, tons of PR not merged. For me it means « unmaitained ». It does not handle all webpack 4 stuff (agressive code splitting), it is not compatible with React Strict Mode.

Also it is just facts, if you are confident about it feel free to use it!

@dickenwong
Copy link

@oyeanuj @theKashey thanks!!

You're right. i didn't really pay attention to how "unmaintained" it is already.

Surely will try this library from now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants