-
Notifications
You must be signed in to change notification settings - Fork 34
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
Interoperability with react-async-component #51
Comments
@ctrlplusb (sorry for the tag) Would be really great if you could look into this ASAP :) Would love to get this scenario working :) |
@SathishGovindaraju I take back the earlier comment. Actually, on further investigation of your issue, it seemed similar to what I was facing in #56 and to me, seems like a issue on |
Just thought I'd say this is all working for me. Try wrapping your resolve function in a promise. Maybe React Jobs is needing that. If that doesn't work, next try using the old webpack require.ensure instead of import. It's been close to a year so I can't even remember why I came to this (Lol), but here's how I do it and it works...
|
@oyeanuj and @unleashit Thanks for your replies. I got it working without the need for |
I've added a demo of this here: https://razzle-async-components-and-data.now.sh/ Source linked 👍 |
@ctrlplusb Seems like the above link isn't working. Could you point me to the source if the link is down? |
Thanks for all the nice libraries :)
I am finding it hard to make this
react-async-component
work withreact-jobs
. The following scenario does not work. Looks like it doesn't resolve the dynamic import before rendering. I usereact-async-bootstrapper
to do server-side rendering as described in the README.AsyncHomePage
is not rendered in the above scenario. Looks like the dynamic-import is not resolved on the server-side.Having said that, the following works when I change the order.
Now instead of passing
AsyncHomePage
to theDependencyResolver
, I am passing the normal component and dynamically import theDependencyResolver
The text was updated successfully, but these errors were encountered: