All 12 useState & useEffect Mistakes Junior React Developers Still Make in 2024
Вставка
- Опубліковано 28 тра 2024
- Hi, I'm Wesley. I'm a brand ambassador for Kinde (paid sponsorship).
👉 Add auth to your app FAST: bit.ly/3QOe1Bh
👉 NEW React & Next.js Course: bytegrad.com/courses/professi...
👉 Professional JavaScript Course: bytegrad.com/courses/professi...
👉 Professional CSS Course: bytegrad.com/courses/professi...
👉 Discord: all my courses have a private Discord where I actively participate
🔔 Email newsletter (BIG update soon): email.bytegrad.com
⏱️ Timestamps:
0:00 Intro
0:06 12/12 - State updates aren't immediate
2:35 11/12 - Conditional rendering
4:46 10/12 - Updating object state
7:59 9/12 - 1 Object state instead of multiple smaller ones
11:25 8/12 - Information can be derived from state / props
14:32 7/12 - Primitives vs non-primitives
19:05 6/12 - Initializing state with object
22:12 5/12 - TypeScript mistakes
27:19 4/12 - Not using custom hooks
30:59 3/12 - Server & Client components
33:08 2/12 - Stale closure
38:42 1/12 - Fetching in useEffect
#webdevelopment #programming #coding
I am a grumpy and impatient senior dev who was soothed by your calm voice and clear explanations. Also learnt a few things. Thanks.
I am a self-taught frontend developer. I know many teachers who teach online, but trust me, the way you explain things is so easy to understand. To me, you are the best teacher. I can't thank you enough. If I had money, I would have definitely bought your courses. Anyways Thank you so much for giving us your valuable time, and I love you.
react is a steaming pile of hot garbage.. lol..
@@nonefvnfvnjnjnjevjenjvonej3384 no cap
I am now quite experimented with React and already knew everything you covered in the video. But I still want to say that this video is pure bomb. The amount of useful information contained in it is quite impressive and really straight to the point. I would have love to have seen it about a year ago. :)
Haha thanks, appreciate it
same here, I just came to see the content but it's really helpful for the beginners, at some point I was making all these mistakes
@@Endrit719 Us bro us.
For me, as a backend developer it’s a pure gem. Everything I should keep in mind in a one video. So easy to refresh knowledge when I had to make some UI parts.
I definitely prefer multiple returns. Most components end up with distinct states that make breaking it down into more declarative components easier to follow. This a personal choice I adopted from React Query tutorials.
if(loading){
return
}
if(error){
return
}
return
If you add a key to PostBody then React will identify each of those components as unique. That will eliminate the race condition and reduce the dependencies in the useEffect Array. Loved your explanation of the setInterval. I never quite understood the problem there.
I do multiple returns as well because if not, one return can become into a return hell, hard to read and follow
cant we just say:
{loading ? : error ? : }
@@pete531 Yes, but that's not very readable and scalable.
I prefer that way too
@@pete531 most teams I've been on ban nested ternaries to avoid complication in logic that is already highly complex.
Brother you solved many of my doubts. You have no idea how helpful and important these kind of videos are for me. Keep making such videos. Full support mate!
Glad to hear that
@@ByteGrad Thank You Brother 🙏
Man after learning Solid and Svelte, I'm starting to find React to be so convoluted.
Because it always was. Even with better alternatives (Solid and Svelte as you've mentioned... and more), to this day so many React devs are living with a React copium
It is
@@DEVDerrit's not copium, I just want an existing ecosystem of packages. Component libraries, styling solutions, utility components, specific solutions libraries etc. They all exist for react and not svelte nor Solid
@@DEVDerr They aren't living with copium, they're living with jobs.
@@Angeal98 You can always search for general, not tied to frameworks solutions. Those exist and there is quite a lot of them.
This is crazy how much you've blown up in the last month! I saw you've created nearly 400 videos in one year, getting 50-100 views per video until recently! It's really inspiring how you never gave up!
Absolutely fantastic video. As a kinda newbie to NextJS and REACT, I was happy that I'd figured out most of these on my own, but some of them (the object item name in brackets trick) will really help get my code leaner.
One of the best videos on React!!!! I've been working as a dev with react for over 1 year now and there were a lot of things in this video that I did not know! Most online courses never fully explain what happens underneath the hood, so thank you!!!
The first case actually helped me a lot! At my job I was fixing a bug and couldn't figure out why component state was behaving wierdly, tourns out it was the multiple setState (although not direct) calls in one useEffect that were the problem
Wow bro. You nailed almost all those doubts i had ever in my react journey. You are a perfect teacher with the soothening voice which actually dragged me to listen to this 40mins lecture peacefully with no breaks.
I really love how direct and precise it is with handle certain react problems. Please do more of this format of videos.I learnt a lot and I appreciate you man. Keep it up
이야 강의가 너무 기가 막혀요🥰👍 궁금했던 부분을 시원하게 긁어주는 기분이네요 감사합니당
I am a self-learning newbie in React and you sir just made learning React a lot easier! Simple, straight to the point, no unnecessary stuff. The time I saved by watching this video instead of scouring the docs is priceless. Thank you very much.
I've been developing JS for 25 years, so I'm not really making the mistakes you list, but I'm only two weeks into React and this was a great crash course on its basic mechanisms. Between the lines, you managed to make it much more clear than the horrible hand-wavy official documentation which reads like it was written by people who don't know the basics of the language.
Do you like hooks overall? I'm around 15 years into JS development. But I hate functional programming with all that half/solutions. Why would anyone prefer functions over better structured, more clean classes (long awaited) syntax and OOP approach in general? 🤷♂
@@IgorYatskiv I started React development when hooks were not yet available, and I like this new functional approach much more. I very rarely have to resort to creating any classes in very special cases.
The way I see it, classes in JavaScript and TypeScript are a less-than-useful hack that don't work in any way like I'd expect. For me, the simplicity of prototypal inheritance, functions and closures are the beautiful bits of the language. That said, I think the state of the JS/TS ecosystem is really sad and avoid it whenever possible, even though I love writing JavaScript.
Great one! Straight to the point, typical and practical life examples! Keep it up and the volume a bit up for the future videos haha
A really great run through of correct patterns and component lifecycles mate, As someone who is 2 years into react, and 9 months or so into ts, I found this a really nice way to confirm my existing understanding, and clear up a few points I had only somewhat understood. Thanks for this :)
The best thing happened to me in recent times is your video popping up on my youtube homepage suggestions.
So much clarity and valuable information.
Subscribed and will surely recommend your channel to every React dev in my circle
38:34 If you leave it as is, your "setInterval" would never be canceled until you close or reload the page. If you call setInterval or setTimeout inside useEffect, always destroy that interval / timeout.
You somehow have managed to address every one of my concerns or gaps I believed I had in my knowledge across all your videos on react and Javascript. Thank you 🙏
That's awesome!
This was really helpful, I recognize a few mistakes I've done and though I've worked around the errors, your explanations gave me a better understanding to why I saw errors or such. Really cool vid and most of all thanks for sharing. I've just recently gotten serious about next.js but before that I used to fetch data in a useEffect much like you said
As a learning developer, I run across hundreds of baity videos, but this one was really useful
Nice touch flipping the video as you move from editor to console 😄
Very helpful vids thx
thanks a lot, useful video. i'm not a begginer but often i don't think about to do some more cleaner if it works. you have fixed my mind
quick counter point on the 8:01 topic, using a single object to store the state of all the inputs will produce a lot of objects, the garbage collector will run more times and the component will update all the inputs that depend on the `useState` which can, some times, reduce performance significantly. By using separate states your component will update way less and create less objects and use less garbage collection cicles
Thank you so much. I love the way you teaching. I working as a junior react developer for 2 years already, but still this video helps me a lot. Great job
Fantastic video! First one of yours I've come across (thanks UA-cam). I'm now a subscriber
I already knew that we can use one big useState but I had likely forgot it and still used multiples. Thanks for telling these!
Amazing. I made all of these mistakes when I started with React some years ago. Hope every React beginner's can watch this.
I learnt all these things by trial and error while using react in my project. This is such a brilliant video that is going to help any new developer starting with react/nextjs to avoid the pitfalls.
This video is jampacked with information. Such an amazing channel.
I just got through a week of useState and useEffect, and this video helped answer a lot of questions. Keep it up man!
This video shows how counterintuitive React is!
Saw this video, loved your straight to the point style and even bought your JS course for the projects it covers. Thanks
learned so much! thank you for the video!
It's always so good to get a basic understanding like this!
Great video. These quick reminders are very helpful! Especially because you often see multiple ways of doing the same thing but no one explains why it works.
For the last one, tbh I would just use a debounce with no leading trigger. Since then no network call goes out and only fires once you’ve “settled”
This way you never hammer ur server until the user has essentially stopped
Can you elaborate a bit on how you would achieve that in Nextjs?
Errr, this isn’t a framework thing, just javascript.
Say you just use lodash.debounce, it would basically just be
Const myDebouncedFn = _.debounce(myFn, 250, { leading: false });
And then just swap the method out in this case for the video
My thoughts exactly. Either that or disable the button while the HTTP call is running
Not only Junior React developers but also mids, so called seniors and all kind of full-stacks who have no idea about JS. Fantastic video :)
Thanks! Great for me as a new React Developer from Angular
Thank you so much for this amazing video!
That's amazing thank you a lot for this video!
as a junior dev, this video certainly helped me solve a lot of issues I had with my code, thank you!
really, really good explanation of everything! thanks a lot for that video. would love to see more.
this is pure gold, thanks a lot!
Great video! You really take the time to explain everything and you do it very well
I am about to learn react in typescript, and really appreciate your video. It really helps me understand about react hooks and how to do it properly. Hope your days will be great, thank you
Been a while since I touched React, and when I did try it out, I just did a few small projects. It was a good intro, but I feel like I retained little. But watching this was so much fun. I'm excited to try it again soon!
Great Explanation. Thanks!!!
17:00 best explanation
Amazing video, watching it from start to finish. Loved it. A React Context and prop drilling best practices would be be amazing as well
I have just started learning react and this video was extremely helpful. It's super clear and understandable. Thank you.
Thank you for this video. #9 really helped me out!
Incredibly dense content full of nice tricks, best practices and clear concepts explanations. It felt like learning "the right way" of coding things in modern JS. This is the first video I watch from you and it made me buy your Udemy JS course. I'll be spending the day watching it. Looking forward for a TS course :) Cheers from Belgium !
Thx for the comment. I should look for his course online. I always study javascript with Stephen Grider; thought he was the top dog.
Great video! I love the way you teach!
Thank you for all the effort you put into this! 🙂
I gotta thank the algorithm for recommending me this video, Wesley! You solved so many things that I was curious in the past! And with Udemy having a big sales event atm I might just grab both of your CSS + JS courses!
Likewise. Video has been helpful. I have several years of experience with JS, CSS, HTML, etc, but only been using React for 6 months or so. Just learned about using Vite over CRA the other day 😅 Hopefully I can land a React job soon!
Thank you so much. I learned a lot
and just when i say i grasped react here bytegrad comes to drop new knowledge , thank you sir again i learned css and js from you ! now i cant wait for your nextjs course i was planning to learn it in the future. you really changing my life :,)
Thanks you very much, I ran through this situation
The video is totally necessary! Good job dude!
As a beginner in React , I can confidently say that this video is a must watch
Amazing content and the way of explanation (smooth and calm). Keep it up, would love to see more on React/TypeScript and probably Jest in the future :)
Thank you for the insights. You clarified my doubts with this video with mistakes that I overlook those features sometimes even I work on them. Thank you for helping out to everyone sharing your knowledge in react and other tech stack.
This video is amazing! Kudos. It warms my heart that I am still an intern and all of this is basically muscle memory at this point.
11/12 - If you still need to call hooks only if a certain condition is met (like on 03:24), which is often the case in practice, you can:
1) return "No id provided" if there's no id
2) copy and paste the code between the lines 6 and 11 into a separate component in which you call those hooks indiscriminately.
3) return that component instead of lines 6-11.
Last tip is good but abort controller will not abort calls on the api side which can further stress the api server in some cases.
I finally understood the relevance of the spread ... operator with your real world example. Thanks to you
The fact that I could guess every solution as soon as you started presenting the problem really makes me happy of my evolution as a react developer.
Congrats buddy! 😉
me too, I can't believe my self either..
With this video I lerned more in an hour than what I learned in one and a half day searching. Thanks!
I watched all the other UA-camrs and their covering of these similar topics. You by far do it the best!
As others have said you are a fantastic teacher. Please make a course on Qwik. We need a voice like yours.
As a rookie reactjs developer i skipped many fundamentals and jumped straight to the code. Now i see how such concepts was important. thx for your time doing such a helpful video.
This is an amazing video, thank you dude.
Great video especially the pace at what you presented. It was 👌No time wasting and just kept going.
Excellent video. For the stale enclosure section, you should still have the clean up function for the setTimeout even if you are using the setCount((current) => count +1) method. The interval needs to be cleaned up when the component is unmounted.
This is 46 minutes of pure gold! Thank you!
Not just junior’s , it was really helpfull for me as a senior dev. Subscribed❤️
Great video, thank you for creating this.
glad I watched this video because I learned more things and I can use the form object state for the first React project I'm currently doing 😊
I new all of them except for the last one, amazing!
21:55 You could also check if the post is null or not and use that to show if it's loading or not. Helpful video btw 👍
Thanks for the video, really helped me a lot ! Especially the 12/12 helped me to understand why my states weren't getting updated xD
4/12 - I always try to avoid duplication in my code however, I obey the Rule of Three of "Rules of Thumb" as well. If the logic isn't too long and/or complicated, I might tend to duplicate it instead of abstracting it until the third duplication.
2/12 - not cleaning the interval causes incrementing the count by 2 on my side.
Thanks, appreciate it!
Great tips! Thanks a lot!
thanks so much for sharing this info for free because I never saw a free course giving like this useful info. You are from the rare people man ❤
this was great, thanks!
Super useful, thank you!
Hey! thanks for the video. I would create an inner component that handle the hooks instead of execute hooks if the ID was missing... Also I won't use an object in the form, since I don't need those extra renders, instead you can use a ref (useRef) to prevent re-render the component N times. Adding the signal to the fetch is ok but you still will call the API N times, instead you can use useEffect with an isFetching variable or loading or whatever you want... and prevent those API calls.
Loved the video. Subbed 🙌
Nice video, I'm on my first big React project and your video helps me a lot, thank you very much!
this content is really helpful. the nuances discussed are both detailed yet put in simple language. thanks alot
Thank you for the video. Very useful stuff to keep in mind!
In the first section, I think it's important to point out that the setCount function call isn't really being "scheduled".
What happens is the function is run top to bottom (it renders the component), and the handleClick function is loaded and attached to the button with the current value of count. When the button is clicked, count is the same for all calls of setCount.
For example, if you put a loop inside the handleClick function that takes 5 minutes to complete in between two setCount calls, one button click will still result in a single increment. Promisifying and awaiting has the same effect.
Thanks for saying this. This and some of the other explanations and examples in this video are very misleading and sometimes even flat wrong. It’s crazy how many people are just admiring the effort and taking it at face value without noticing the mistakes/problems. Another obvious example is the explanation about fetching data in useEffect without addressing the asynchronous nature of the fetch api and including practically required concepts such as async/await… There are other bad examples such as the resize listener which if declared as per the example will clear all resize listeners across the whole application and etc. I can keep going, but essentially almost every single example in this video has an issue. And we wonder why junior developers make such mistakes… because they watch videos like this one which demonstrate one type of error only to replace it with another…
Great video, thanx !!
Fluidity and conciseness. Thanks!
Wow this was super valuable. Thank you 🙏
I like that all the details are also discussed. Great video.
Thanks for the tips that was very smooth
You explain it so good brother, thank you!
This is an excellent refresher for intermediate react devs. Thanks 🙏
This is fantastic! Thanks a lot
this explains a lot !!!!! i now understand!!!! thank you🙏