-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Apply ssr to some components #54
Comments
When we were building a site about Silicon Beach Tech Consulting we faced the same issue and on research came across this answer by @choonkending on reactgo
Lifecycle
|
@czco Thanks a lot, I will try this solution and inform you if it is helpful or not. |
@SamaneYaghoobi no problem, did it work? |
@czco I read the issue that you linked and I think it doesn't related to Razzle and won't work. |
@SamaneYaghoobi razzle? what does razzle have to do with anything? we would love to provide an example but it looks like the authors of this repo aren't providing much support, we had to move a live project back to next.js. In any SSR framework this is how you make sure component doesnt not get rendered on the server |
Hey, my apologies for the long wait @SamaneYaghoobi - I'm looking to ensure this is fixed with version 2.0. If you're interested, I could really use your thoughts for what you'd like to see in the upcoming version. Feel free to comment on the issue here with any suggestions. :) @czco I know it may be a bit late since you've already switched to Next.js. My apologies for the lack of progress. |
Hi @cereallarceny, |
I updated it before I knew about Razzle, which I now suggest you use. It's
basically what I was intending to build for version 2.
|
@cereallarceny |
Hi, I want to know what should I do to apply ssr just to some components and other components or routes rendering client side as normal way?
The text was updated successfully, but these errors were encountered: