Hi, my latest course is out now (Professional React & Next.js): bytegrad.com/courses/professional-react-nextjs -- I'm very proud of this course, my best work! I'm also a brand ambassador for Kinde (paid sponsorship). Check out Kinde for authentication and more bit.ly/3QOe1Bh
Do you offer regional discounts like some other authors, taking in account students country? (like South Africa with a very weak Rand to the US Dollar)
you are THE ONLY ONE who actually is trying to explain this on examples which aren't complete copies of the documentation together with the same, exactly the same, explanation. I'm so thankful I can't even express this properly in words, it's very frustrating to look for some explanations and just getting these videos with the exact documentation copy paste with 0 info over and over and over again...... man
this is best nextjs video. Majority of yt is filled with just basic tutorials and it's so hard to find videos like this. Everyone is discussing new Nextjs features instead of actually teaching about features used in Industry.
What I love about this video is how you go through each example and insert those "oh, and btw you can also do this this other way, and this will work a little different, which may or may not be better in your use case". That's always what lack in tutorials. Everyryone is teach only one, their, strict way, and if you try to deviate from that for an inch, then everything falls aparat, but they won't tell you that!
Well, this video alone is more valuable than most courses about Next.js. Almost all mistakes solved in this video are from real-life struggles and can easily take tons of hours to figure out how to solve them alone! Thank you for the amazing video! I was hesitant to upgrade to Next 15 because of these doubts I had about server/client components. This video helped me a lot. :D
I just wanted to say thanks for creating such a great video on hydration issues and client/server component mixing in Next.js! I've been struggling with this concept for a while, but your video finally nailed it. I've been watching Next.js videos nonstop since Next.js 13, and yours was the one that finally made sense to me. I'm still on a tight budget right now, but your course is on my list. I've subscribed and am looking forward to checking out your other videos!
This is gold, thank you. Well explained, especially the server/client component differences and woes, such as Hydration errors. Extra Side Note: I rarely, if ever, watch a 2h video tutorial in one go, so kudos for keeping it extremely relevant for Next.js devs :)
Way to get to the f'ng point on every one of these! I typically can't sit through long instructional videos...they're so often filled with fluff. I find myself skipping through them looking for actual content and (typically) giving up. But this was an easy 1hr and 45 to watch every single minute of. Hats off.
"Insightful video! It's no mistake to say this is the #1 Next.js guide for beginners. Your comprehensive rundown cleared the fog surrounding many common misconceptions. Time to level up our digital marketing game with Semaphor analytics. Thank you!"
the amount of information in this video is purely gold, you are probably the best React/Nextjs instructor man, thank you so much for all of the efforts and time!
bro you are the one and only one kind of a teacher who has explained the concepts like a teacher teaches to kids , minimalistically yet on to the point , I will be buying your course , I am from India and even after the discount price is still high for me , I am gonna save and bring your react next course , please dont stop content like this , your explanations are best , also please start series like this for react and other , Also please start project series , i feel no other teacher can match the style when it comes to build complex apps on youtube , so please go ahead with projects tutorials.
Слушай, а это все понятно когда мы использует fetch и чистый next js. А что если мой сервер с базой данных находится не в проекте next js. А где то на другом сервере. Я обращаюсь к нему посредством rest api. Я пытаюсь прикрутить в свой next js проект tanstak query. Я думаю что это будет лучшим решением чем то что предлагает next js из коробки. Мне интересно твоё мнение.
this is not only the best nextjs video I've watched, it is also one of the best overall programming videos I've ever watched. I can't stress enough how useful this is. thank you so much!!!
This video is an absolute gem! 🌟 The explanation of the Next.js app router and pages router differences was incredibly clear and helpful. The examples provided on server components and client components really made it easy to understand where to use each. I especially appreciated the deep dive into hydration errors and how to handle them. Keep up the great work! 🚀👏
After the first few sections, I ended up watching the entire video. You do an excellent job of providing real world scenarios and examples on the topics, as well as explaining the alternative of your advice. Awesome work
I have seen quite a lot of NextJS videos on TH-cam and also courses from Udemy. This is the BEST so far. Practical examples to demonstrate the mistakes. And most importantly it rephrases those big terms we see in documentation in a layman way that beginner can understand. Thanks for the video
GREAT VIDEO! Giving real world examples that are at the same time generic is best way to convey the knowledge. Even if I often read documentations and articles, I learned a lot of new things from this video and see some of my mistakes from the past, that I resolved but didn't know why was it resolved. THANK YOU for this!
I'm just around half way there in the video & feeling like I have watched hours long tutorial. Highly appreciate the content! Highly appreciate your efforts & knowledge! Bundle of thanks!
One of the best video on NextJS doubts which will only arise once you become expert in NextJS after completing FEW videos FEW projects. But your video is so amazing that if any dev will watch it completely will definitely become pro in NextJS and any confusion which used to come when we do large project will be cleared out after watching this, Thanks :) Much love from India.
Amazing! Awesome! Fabulous! You have explained ALL what all common confusions go on with NextJs. NextJs should include this video in their official guides and help/troubleshoot/Faqs docs. This cleared most of my doubts for which I was not finding a fitting resolutions together combined anywhere else. ❤ Thanks alot #ByteGrad
@@ByteGrad One thing doubt remains, when I have to use header on all page, or authentications , how to make sure not all pages become dynamic rendered? U said middleware word, but that not explained. What is real solution?
Middleware is a special file you create at the root of your next js project. This file is where you put all your authentication logic. Just like loading, error, route and page files have a special meaning in next js, a middleware file would automatically be recognized by next js and would be run by next js before the routes you specify in the matcher of helper function written in your middleware file.
this video is the best out there, I'm happy that I found it, but sad that it took me so long to get to this golden gem. very nice work, hope you keep sharing your knowledge.
This was one of the best deliveries i have seen outside of dave gray. Will be picking up that course, and hoping it is delivered with the same clarity.
Not even halfway through. AMAZING. I have learned some of the subtle dance between client and server. Thank you, I thought I was going crazy. Question about your course (React + Next): Do you provide a pattern of Client > Next Auth > Server > Database > Back to Client > Edit/Update/Upsert > Revalidate? Or something close? If not, can I request a paid consultation?
Thanks, I made exactly the most of the mistakes you are mentioning here. My problem with "use client" overuse was very painful, as I was getting 429 from the external service that I'm using for auth. The problem was, I was fetching data on the server side but the call went from client component, so through the middleware I had many requests on a single render of a all components, causing 429 on user check and token refresh. A tough lesson learned - I wish I’d seen your video sooner!
It's funny cause I just made the mistake of using "use client" wherever I got an error just to get around it without actually understanding it and the first video I get recommended is yours, almost ironic. Thank you so much though this video saved so much time for me with my first project!
Nice overview! I have some experience with React and started learning NextJs. Currently, I'm building a full-stack app, and for a front-end I decided to use NextJs. So your video is a good reminder of which mistakes need to be avoided.
wow man, you need to be ambassdor of vercel, a missile of bottom lines what a implicity sharp gzipped explaination worth every second congratz you pinned as top mentor on next js
1. Thinking that client components only run in the client. 2. Using browser api's 3. Hydration errors (how to suppress it). 4. Incorrectly dealing with third-party components. 5. Fetching in different places were a problem 6. Forgetting key props with Suspense 7. Using redirect in try catch
Great video, bro! I learned a lot more than I did from the Next.js documentation because you explained things thoroughly. Thanks a lot for your hard work.
This video is super relevant, I learned a lot of things, I found out that I was not validating my server actions, I'll have to address this because I thought that nextjs automatically validated them but now that I think, there's now way that next will know what type things are for validation, this is just a typescript layer. I have to come up with a nice validation strategy for keeping types but knowing that it can be unknow data for server actions.
wowzers! this was awesome 2 hours! agreed with comments above, mistakes you were showing, was the mistakes i made in a some of my previous projects great job! subscribed!
A deficiency Next.js data caching has is that if the same fetch is called in multiple components on the same page, the first cache miss (e.g. build) will cause all of the components to fetch the same data (in parallel) and all of them will set the cache. There should be an easy way to dedupe the calls happening at the same time and let only one of the components go to the network and set the cache. E.g. first component to trigger the fetch makes others wait. After that, the components can get it from the cache. If the thing being fetched is cheap, yeah no problem, but if it's rate limited or takes a long time, although it can be rendered in parallel on the server, it's still unnecessary work.
Coming from other ssr frameworks it’s absolutely terrifying using web APIs causes next to entirely collapse without specifying magic words use client. Just something you don’t need to think about in other frameworks.
I normally dislike youtube videos to learn about frameworks and programming but, I believe nextjs documentation is way too high level and as soon as you hit some specific problem is rather useless. As many others said, this cleared a lot of my confusion with nextJS, thank you.
What a video. This video covers almost everything about RSC... Thank you... there is one thing left in my head that keeps making me stuck on my project. "where do we save token and refresh token". since my project depends on an external data source that require access token and reguilarly refresh the token with he give refreshToken. In client side, we commonly do it in cookie, and using axios we can pass that token as bearer token, and with the interceptor we refresh the token if necessary. but what is your advice when it comes to server land?
I spent last 3 months learning NEXTJs(Switching from react to next) and some things just didn't make sense although I'm pretty good with react. This one video simplified entire Nextjs for me. Thanks a lot brother. I'm eternally grateful.. Now it all makes complete sense.
I have one question....can you explain the purpose of wrapping a server component with a context provider? Can the context share data to the server component or its just to allow server components to be redered as server? And thank you for this tutorial, it helped me a lot!
Awesome video! I'm a bit confused about "getData" functions and the "use server" directive. We shouldn't place "use server" at the top of a file which has a bunch of "getData" functions, because we are exposing a POST endpoint, and also because calling a "getData" from a server component already make the get in the server. We should use "use server" only to mutations functions, and validate those. Did I get that right?
So I answer myself after some investigation. React recommends to use "server-actions" for mutating. According to React docs "Server Actions are designed for mutations that update server-side state; they are not recommended for data fetching.". You could use it to retrieve information but is not the intended way. Server actions request is a POST, so you will be fetching data with a POST request. I found in a Reddit post this answer: "I asked one of the members of the Vercel team on Discord if we could use server actions to fetch data. While it's possible, they don't encourage this, but the response I got was a bit ambiguous."
This video is really good. I’ve just finished reading the docs and you just filled all the blanks in my mind. Btw, what Vs code theme are you using? Thx
How would you advise using a state management library like zustand to handle, fetch, stored responses, to be used it a page let's say "analytics". You know eventually every component will def be a use client component, since every component needs that stored data. Is it best to ditch the zustand sml and just use the next.js inbuilt async mechanism to fetch those data individually on each components, or ...?
I would like to send the user to a different webpage. For example: When a user clicks a button, an API call is made; based on the response, need to redirect user to a different page. I have used useRouter from next/navigation. The page reloads and gets redirected. its not redirecting client side NEXT VERSION: 14.2
Hi, my latest course is out now (Professional React & Next.js): bytegrad.com/courses/professional-react-nextjs -- I'm very proud of this course, my best work!
I'm also a brand ambassador for Kinde (paid sponsorship). Check out Kinde for authentication and more bit.ly/3QOe1Bh
Do you offer regional discounts like some other authors, taking in account students country? (like South Africa with a very weak Rand to the US Dollar)
@@niconel7659 also, for India?
you are THE ONLY ONE who actually is trying to explain this on examples which aren't complete copies of the documentation together with the same, exactly the same, explanation. I'm so thankful I can't even express this properly in words, it's very frustrating to look for some explanations and just getting these videos with the exact documentation copy paste with 0 info over and over and over again...... man
Thanks!
Agreed
Byte Grad is super smart, another amazing video
Exactly
agreed agreed agreed❤
this is best nextjs video.
Majority of yt is filled with just basic tutorials and it's so hard to find videos like this.
Everyone is discussing new Nextjs features instead of actually teaching about features used in Industry.
What I love about this video is how you go through each example and insert those "oh, and btw you can also do this this other way, and this will work a little different, which may or may not be better in your use case". That's always what lack in tutorials. Everyryone is teach only one, their, strict way, and if you try to deviate from that for an inch, then everything falls aparat, but they won't tell you that!
Well, this video alone is more valuable than most courses about Next.js.
Almost all mistakes solved in this video are from real-life struggles and can easily take tons of hours to figure out how to solve them alone!
Thank you for the amazing video!
I was hesitant to upgrade to Next 15 because of these doubts I had about server/client components. This video helped me a lot. :D
I've been working with Nextjs for two years and you made me aware of so much mistakes I made in past projects. Great video.
This video felt like 10 minutes to watch. Improved many things in my current project because of you. Thank you
I watched the video for a bit and didn't realize I've watched it for 1 hour. Yes, it indeed felt like a 10 minute video XD
I just wanted to say thanks for creating such a great video on hydration issues and client/server component mixing in Next.js! I've been struggling with this concept for a while, but your video finally nailed it. I've been watching Next.js videos nonstop since Next.js 13, and yours was the one that finally made sense to me. I'm still on a tight budget right now, but your course is on my list. I've subscribed and am looking forward to checking out your other videos!
Enjoy!
This is gold, thank you. Well explained, especially the server/client component differences and woes, such as Hydration errors.
Extra Side Note: I rarely, if ever, watch a 2h video tutorial in one go, so kudos for keeping it extremely relevant for Next.js devs :)
Glad it was helpful!
Way to get to the f'ng point on every one of these! I typically can't sit through long instructional videos...they're so often filled with fluff. I find myself skipping through them looking for actual content and (typically) giving up. But this was an easy 1hr and 45 to watch every single minute of. Hats off.
This video is absolutely masterpiece!! Thank you!!
This is pretty much becoming my favorite video on the internet right now
This is actually the #1 next js video for beginners. You cleared up so much of my confusion
"Insightful video! It's no mistake to say this is the #1 Next.js guide for beginners. Your comprehensive rundown cleared the fog surrounding many common misconceptions. Time to level up our digital marketing game with Semaphor analytics. Thank you!"
the amount of information in this video is purely gold, you are probably the best React/Nextjs instructor man, thank you so much for all of the efforts and time!
bro you are the one and only one kind of a teacher who has explained the concepts like a teacher teaches to kids , minimalistically yet on to the point , I will be buying your course , I am from India and even after the discount price is still high for me , I am gonna save and bring your react next course , please dont stop content like this , your explanations are best , also please start series like this for react and other , Also please start project series , i feel no other teacher can match the style when it comes to build complex apps on youtube , so please go ahead with projects tutorials.
Awesome, thanks!
Ты молодец. Именно этой информации мне не хватало и именно её так тяжело найти на просторах интернета. Ты лучший
Слушай, а это все понятно когда мы использует fetch и чистый next js. А что если мой сервер с базой данных находится не в проекте next js. А где то на другом сервере. Я обращаюсь к нему посредством rest api. Я пытаюсь прикрутить в свой next js проект tanstak query. Я думаю что это будет лучшим решением чем то что предлагает next js из коробки. Мне интересно твоё мнение.
this is not only the best nextjs video I've watched, it is also one of the best overall programming videos I've ever watched. I can't stress enough how useful this is. thank you so much!!!
This video is an absolute gem! 🌟 The explanation of the Next.js app router and pages router differences was incredibly clear and helpful. The examples provided on server components and client components really made it easy to understand where to use each. I especially appreciated the deep dive into hydration errors and how to handle them. Keep up the great work! 🚀👏
After the first few sections, I ended up watching the entire video. You do an excellent job of providing real world scenarios and examples on the topics, as well as explaining the alternative of your advice. Awesome work
I have seen quite a lot of NextJS videos on TH-cam and also courses from Udemy. This is the BEST so far. Practical examples to demonstrate the mistakes. And most importantly it rephrases those big terms we see in documentation in a layman way that beginner can understand. Thanks for the video
Such a quality content with so robust explanation and presentation. Not many creators do that. Thanks, it was pleasure to watch and learn from it.
Much appreciated!
Great video. I am only 20mins in and it has already cleared up server/client confusion I had while starting to work with Nextjs.
Nice!
GREAT VIDEO! Giving real world examples that are at the same time generic is best way to convey the knowledge. Even if I often read documentations and articles, I learned a lot of new things from this video and see some of my mistakes from the past, that I resolved but didn't know why was it resolved. THANK YOU for this!
I'm just around half way there in the video & feeling like I have watched hours long tutorial. Highly appreciate the content! Highly appreciate your efforts & knowledge! Bundle of thanks!
so much better than those vercel guys that literally do documentation voiceover as if people can't read
One of the best video on NextJS doubts which will only arise once you become expert in NextJS after completing FEW videos FEW projects.
But your video is so amazing that if any dev will watch it completely will definitely become pro in NextJS and any confusion which used to come when we do large project will be cleared out after watching this,
Thanks :)
Much love from India.
This type of explanation I've never seen on youtube, once again thank you for your efforts.
Amazing! Awesome! Fabulous! You have explained ALL what all common confusions go on with NextJs. NextJs should include this video in their official guides and help/troubleshoot/Faqs docs. This cleared most of my doubts for which I was not finding a fitting resolutions together combined anywhere else. ❤ Thanks alot #ByteGrad
Thanks, enjoy!
@@ByteGrad One thing doubt remains, when I have to use header on all page, or authentications , how to make sure not all pages become dynamic rendered? U said middleware word, but that not explained. What is real solution?
Middleware is a special file you create at the root of your next js project. This file is where you put all your authentication logic. Just like loading, error, route and page files have a special meaning in next js, a middleware file would automatically be recognized by next js and would be run by next js before the routes you specify in the matcher of helper function written in your middleware file.
Just waiting for my CC turn to buy your course. You are , by far, the best teacher i ever had. Greetings from Brazil!
this video is the best out there, I'm happy that I found it, but sad that it took me so long to get to this golden gem. very nice work, hope you keep sharing your knowledge.
This was one of the best deliveries i have seen outside of dave gray. Will be picking up that course, and hoping it is delivered with the same clarity.
Awesome, enjoy!
Watch this video every once in a while because it's golden
Not even halfway through. AMAZING. I have learned some of the subtle dance between client and server. Thank you, I thought I was going crazy. Question about your course (React + Next): Do you provide a pattern of Client > Next Auth > Server > Database > Back to Client > Edit/Update/Upsert > Revalidate? Or something close? If not, can I request a paid consultation?
Hi, yes CRUD is part of the course
@@ByteGrad Cheers, new subscriber and purchasing course.
Thanks, I made exactly the most of the mistakes you are mentioning here. My problem with "use client" overuse was very painful, as I was getting 429 from the external service that I'm using for auth. The problem was, I was fetching data on the server side but the call went from client component, so through the middleware I had many requests on a single render of a all components, causing 429 on user check and token refresh. A tough lesson learned - I wish I’d seen your video sooner!
best NextJS video on TH-cam & it's not even close
Perfect timing! I'm currently on week 4 of learning Next.js and this video has been very helpful 🤓🙏🏼
It's funny cause I just made the mistake of using "use client" wherever I got an error just to get around it without actually understanding it and the first video I get recommended is yours, almost ironic. Thank you so much though this video saved so much time for me with my first project!
Nice overview! I have some experience with React and started learning NextJs. Currently, I'm building a full-stack app, and for a front-end I decided to use NextJs. So your video is a good reminder of which mistakes need to be avoided.
A lot has been learned here.
Also love how you use TS along with the code. That's professional level.
wow man, you need to be ambassdor of vercel, a missile of bottom lines what a implicity sharp gzipped explaination worth every second congratz you pinned as top mentor on next js
You are the man! This channel is a gold mine for people learning NextJs. Can't praise and recommend you enough!!!
I haven't watched any Next js course. I have just read the documentation and watched your video and I think that I'm pro now. Thank you❤
This is what we need, it clears all the misconception about next js, huge thanks to you sir.
Every minute of this video is called "QUALITY CONTENT"
myyyyyyy heroooo its a treasure for nextjs devs!! really expecting a video like this from you!!
Wow sir you are attempting to do those things which other youtube doesn't focus on thank you sir 🥰🥰😍
This tutorial definetly should have saved thousands of Nextjs devs lol. Was at least 100x better than the nextjs documentation
What an amazing video. Very clarifying!!
Only about half hour into the video, but already learning a lot. Thank you so much for making this
1. Thinking that client components only run in the client.
2. Using browser api's
3. Hydration errors (how to suppress it).
4. Incorrectly dealing with third-party components.
5. Fetching in different places were a problem
6. Forgetting key props with Suspense
7. Using redirect in try catch
really good video. At start i thought it's too fast, but repeating stuff just makes it so clear by the end
Thanks again. The only channel where I am very excited for the new uploaded videos...
Most concise react content creator, thanks a lot for the tutorials!
i am new to nextjs and your video has helped me to understand client and server component difference.
lot of hard work. just 12 minutes into this video and i already liked and subscribed this channel.
Change the title to Mistakes devs make. I’m not a beginner and you made some great points!
Great video, bro! I learned a lot more than I did from the Next.js documentation because you explained things thoroughly. Thanks a lot for your hard work.
This is gold material. You explained the mistakes really well.
The explanation got a bit repetitive though, maybe you can work on that in the future.
hands down, one of the most useful video on next.js. Subscribed.
This video is super relevant, I learned a lot of things, I found out that I was not validating my server actions, I'll have to address this because I thought that nextjs automatically validated them but now that I think, there's now way that next will know what type things are for validation, this is just a typescript layer. I have to come up with a nice validation strategy for keeping types but knowing that it can be unknow data for server actions.
Excellent , this cleared a lot of misconceptions I had and also gave me more clarity on NextJs App router concepts. Thank you.
My god was that well explained. I needed that video months ago when I started my project it would have help soooo much. Thank you for the video
wowzers! this was awesome 2 hours!
agreed with comments above, mistakes you were showing, was the mistakes i made in a some of my previous projects
great job! subscribed!
Intrusive thoughts: Take a shot every time "component" is being said
My brother in Christ are you trying to die?
I find the "use clients" and "use server" weird, NextJS v12 made so much sense, since v13 not so much! Thanks for your videos!!!
29 pitfalls.. makes me wonder why I keep using next.
The learning curve is real, but worth it IMO
the useful tutorial video, i hope you can point out more and more common mistakes that developer can make with Next.js project.
Thanks, will do!
Your course was amazing and your videos are always top tier. I would love it if you could do a database design course/series of videos.
Great to hear, thanks! Will think about your suggestion
A deficiency Next.js data caching has is that if the same fetch is called in multiple components on the same page, the first cache miss (e.g. build) will cause all of the components to fetch the same data (in parallel) and all of them will set the cache. There should be an easy way to dedupe the calls happening at the same time and let only one of the components go to the network and set the cache. E.g. first component to trigger the fetch makes others wait. After that, the components can get it from the cache. If the thing being fetched is cheap, yeah no problem, but if it's rate limited or takes a long time, although it can be rendered in parallel on the server, it's still unnecessary work.
Great information! Just started my first nextjs project and this information really helped alot! I'll refactor some of my code based on it.
Great content. Just bought your course to support you!
Awesome, thank you!
Coming from other ssr frameworks it’s absolutely terrifying using web APIs causes next to entirely collapse without specifying magic words use client. Just something you don’t need to think about in other frameworks.
I normally dislike youtube videos to learn about frameworks and programming but, I believe nextjs documentation is way too high level and as soon as you hit some specific problem is rather useless. As many others said, this cleared a lot of my confusion with nextJS, thank you.
What a video. This video covers almost everything about RSC... Thank you...
there is one thing left in my head that keeps making me stuck on my project.
"where do we save token and refresh token". since my project depends on an external data source that require access token and reguilarly refresh the token with he give refreshToken. In client side, we commonly do it in cookie, and using axios we can pass that token as bearer token, and with the interceptor we refresh the token if necessary.
but what is your advice when it comes to server land?
Highly comprehensive video!
Keep going
This was an awesome knowledge pill! I've watched it in one go and now I understand my code better. Thank you!
exactly what i was looking for. keep it up!
I spent last 3 months learning NEXTJs(Switching from react to next) and some things just didn't make sense although I'm pretty good with react. This one video simplified entire Nextjs for me. Thanks a lot brother. I'm eternally grateful.. Now it all makes complete sense.
amazing video, i started to smell my code and when i went to your video, it was indeed my code was smelly :D
Video is freakishly helpful. Great job buddy.
Thank you for helping me with my current and previous project.
Greatest Next.js video I have ever seen
Really useful knowledge and well explained! So easy to miss some of these when starting with next.js. Thank you!
Thank you, very informative, watched all the way to the end! 😅😇😎
This is an excellent video - I have experienced ALL the problems mentioned here
After understanding all, this is a cool way to make project , we have both client and server components available just we have to decide
This was unbelievably helpful. Thank you so much 🙏🏴
Awesome!! 🎉🎉🎉
PS: how many times have you said "client component"? 😂
It's wild how Vercel brought PHP concepts to the Javascript world
I have one question....can you explain the purpose of wrapping a server component with a context provider? Can the context share data to the server component or its just to allow server components to be redered as server? And thank you for this tutorial, it helped me a lot!
Very informative, this video helped me a lot in understanding nextjs, thank you
Awesome video!
I'm a bit confused about "getData" functions and the "use server" directive. We shouldn't place "use server" at the top of a file which has a bunch of "getData" functions, because we are exposing a POST endpoint, and also because calling a "getData" from a server component already make the get in the server.
We should use "use server" only to mutations functions, and validate those.
Did I get that right?
So I answer myself after some investigation. React recommends to use "server-actions" for mutating. According to React docs "Server Actions are designed for mutations that update server-side state; they are not recommended for data fetching.". You could use it to retrieve information but is not the intended way.
Server actions request is a POST, so you will be fetching data with a POST request.
I found in a Reddit post this answer: "I asked one of the members of the Vercel team on Discord if we could use server actions to fetch data. While it's possible, they don't encourage this, but the response I got was a bit ambiguous."
This video is really good. I’ve just finished reading the docs and you just filled all the blanks in my mind.
Btw, what Vs code theme are you using?
Thx
Big W Sir
You earned a sub, Next God.
you are such kind of superhero , thanks for the lesson
How would you advise using a state management library like zustand to handle, fetch, stored responses, to be used it a page let's say "analytics". You know eventually every component will def be a use client component, since every component needs that stored data. Is it best to ditch the zustand sml and just use the next.js inbuilt async mechanism to fetch those data individually on each components, or ...?
I would like to send the user to a different webpage.
For example: When a user clicks a button, an API call is made; based on the response, need to redirect user to a different page.
I have used useRouter from next/navigation. The page reloads and gets redirected. its not redirecting client side
NEXT VERSION: 14.2
By far the best explanation ever🙌 Thank you
Such an underrated channel!