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

Cooperation with lazy/Suspense #78

Open
wmertens opened this issue Jun 8, 2019 · 3 comments
Open

Cooperation with lazy/Suspense #78

wmertens opened this issue Jun 8, 2019 · 3 comments

Comments

@wmertens
Copy link
Contributor

wmertens commented Jun 8, 2019

I'm wondering if there is a way to use Suspense and lazy on the browser side in some way together with react-imported-component. Are all the functionalities overlapping, or is RIC basically what l+S will be later when it supports SSR?

What will be the future of RIC and l+S?

@theKashey
Copy link
Owner

The future for client side is #77, or another way to prefetch the data, making code splitting more "predictable", and, honestly, removing the original idea about Suspense - death by thousands spinners. The same logic could be used to load React.lazy, as long as it's more about pure import, than anything else.

Plus I dont think l+S would ever "support" SSR, as long as it requires integration with a bundler(like loadable-components), or injection to the code(like RIC) - "React" should not be able to afford it.

@wmertens
Copy link
Contributor Author

wmertens commented Jun 8, 2019

What about the integration with Concurrent React, where lazy() helps React know when to pause rendering? Can that be integrated client-side while the import promise is resolving?

@theKashey
Copy link
Owner

I am looking forward to use React.lazy(with custom thenable) underneath, thus RIP would only orchestrate chunks loading.

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

2 participants