Next.js 14 Tutorial - 47 - Server-side Rendering (SSR)

Рет қаралды 25,910

Күн бұрын

✨ Code snippets - pieces.app/
📘 Frontend Interview Course - learn.codevolution.dev/
💖 Support UPI - support.codevolution.dev/
💖 Support Paypal - www.paypal.me/Codevolution
💾 Github - github.com/gopinav
📱 Follow Codevolution
+ Twitter - / codevolutionweb
+ Facebook - / codevolutionweb
📫 Business - codevolution.business@gmail.com
Next.js 14
Next.js Tutorial
Next.js 14 Tutorial
Next.js Tutorial for Beginners
Server-side Rendering (SSR)
Server Side Rendering in React
SSR

Пікірлер: 20

@roninspect4357 3 күн бұрын

best explanation regarding server sider rendering (SSR) hands down. Thank you!!!

@vinception777 28 күн бұрын

Thank you sooo much, videos 45 to 55 are actually EXACTLY what I was looking for with the schemas and explanations. This is absolute gold, keep up the great work ❤

@jellyfish1772 2 ай бұрын

This was actually valuable knowledge. Thank you

@imagination3124 4 ай бұрын

Literally the best explanation and concept clearerence keep it up bro I am gonna learn whole next js framework from yoy🎉🎉❤

@sakibuddin429 4 ай бұрын

great explanation!!!

@singaporestreettravel 2 ай бұрын

Thanks for super video

@tabotcharlesbessong3756 4 ай бұрын

This explanation will help me for my defense next week

@joshnirohina318 4 күн бұрын

Hope you did well

@tabotcharlesbessong3756 3 күн бұрын

@@joshnirohina318 yes I did thank you 😊

@qocayevmurad222 4 ай бұрын

awesome

@chesterxp508 20 күн бұрын

GoodJob!

@zooz3439 4 ай бұрын

hey mate when will you finish this course?

@HuyLe-tu4pj Ай бұрын

🎉🎉🎉🎉

@imkir4n 4 ай бұрын

Hey vishwas, is it ok if i use Next.js like a React way without middleware, sc data fetching and route handlers?

@ayushkathariya 4 ай бұрын

Yes but in your application if there is any protected route you should use middleware and you should also fetch data In server components and it is ok to use other backend api if you don't use next.js route handlers

@imkir4n 4 ай бұрын

@@ayushkathariya no need of middlewares I can protect route with a HOC. also Middleware currently only supports the Edge runtime. The Node.js runtime can not be used. And im saving token i local storage so how can i authenticate user in server component? to data fetch in the sc i need to attach token in header. Correct me if im wrong and tell me a way to do these things.

@shakti_pattanaik01 4 ай бұрын

@@imkir4nyes.. you can have a cookie which is part of header. In sc you can check if the cookie is expired or not. But you have to figure out a way to refresh that cookie with every request. Supabase/ssr has done a great job with next js and cookies. But they are using a middleware for refreshing the cookie every time there is a new request. Note- next js only allows updating cookies in middleware, server actions and in route handlers, not in server or client components.

@imkir4n 4 ай бұрын

@@shakti_pattanaik01 yah thats the part where im challenging and refused to use nextauth like lib. Token rotation is messed up in that libs. Also opt out for cookie cause some browser/ mode restrict to save cookie. For now token is in local storage and im not using any middleware

@slickdandy 2 ай бұрын

Good explanation, but not a tutorial.

@bla4224 10 күн бұрын

"drawbacks"? Hmmm, I would say "advantages" and less round trips. Unfortunately this isn't really true: the NextJS SSR stuff is not really SSR. NextJS is not able to separate CSR from SSR code correctly (even not for well-known /API functions like getServerSideProps()) and makes very poor decision, which in turn makes this kind of implementation absolutely useless for real world applications. E.g. why do returned props need to be serializable if the component gets SSR? Or why break 'import server-only' functions builds, even if they are used in the mentioned SSR-functions, only? IMHO the NextJS SSR stuff is a total mess and should be clearly avoided just because of this.