-
-
Notifications
You must be signed in to change notification settings - Fork 380
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
loadable-components issues with Asp.Net core SPA (JavascriptServices) #29
Comments
to comment, i might be doing something wrong with my getLoadableState method.
|
It is difficult to help you with this portion of code, but I will try. Is The problem could be that a loadable-components is not present in the React Tree, so it is undetectable for |
NVM, i figured out the issue. i forgot to declare external on my webpack server config: // /
now my Async Server-side rendering works perfectly now! sorry to bother! |
Nice! |
I am attempting to configure Server-side rendering for my Asp.Net core SPA application. the method getLoadableState does not wait for the async components to finish loading. I always get the loading component rendered:
if i do this for each async component, my SSR works:
i have tried the followind posts, but i am still getting issues with Async SSR:
https://marmelab.com/blog/2017/10/17/code-splitting.html
https://medium.com/smooth-code/introducing-loadable-components-%EF%B8%8F-646dd3ab0aa6 (sorry, your intro blogpost)
i have the full server code below, this is being called by an 'asp-prerender-module' taghelper on .Net Core. I am working off the ReactRedux SPA Template without Typescript.
The text was updated successfully, but these errors were encountered: