Hey!, just a simple tip that i use, is when you want to know if an array have elements (means its length is greather than 0), you only have to put array.length instead of array.length > 0, because if array.length is 0, 0 means false, and if is not 0 so is true, sorry if my english is bad.
when i click this video, i only expect to know how to implement infinity scroll. But after 25 minutes i have learned way more than that, like custom hook. Thank you so much
I think this deserves a clarification - it's not just useCallback that can be assigned to an element's ref. Any function can be passed there, you just need to be very careful if the function updates state, since it can cause infinite re-renders. Therefore, in this scenario, Kyle is right to use the useCallback hook, as the function he's using calls setPageNumber. Let's say he used a plain function: the function he's using sets the state at some point, which re-renders the component. When the component gets re-rendered, the function gets reinstantiated. Since it's passed to an element's ref, the element gets re-rendered, which calls the function again. The function changes the state, causing the component to re-render... and we have ourselves an infinite loop.
That useCallback() behavior with useRef() that confused me, now I got it. Thank you Kyle, this is the best explanation about infinite scrolling with react 😍😍
Great to see a video that includes some of the more advanced React features. I'll definitely need to watch this again, which is a feature of the best code run through videos.
Man I have watched literally thousands of paid courses, but no course matches the level of explanation that this guy provides. Simply Amazing. Hats off!
Awesome tutorial man. Straight to the point and well explained. Got an infinite scroll up and working in my application no problem after watching this. Subscribed!
Amazing! Thank you very much, I thought it would be harder to make something like this. Also THANKS because I finally got how to make a custom hook, I was having some struggles to get it.
Thank you for this tutorial! I got something similar workign, I just wanted the "isVisible" for one of my elements to show up. I think this video is a little too long, and getting the custom hook created is a little bit of a side job for getting infinite scrolling, and I would have preferred just getting the "isVisible" working, and then going from there. That being said, thanks for the info, your tutorials are always at a good pace, and I like that you've included the source code!
Didn't realize so little code was required for this. I'm too used to using libraries and I'm not aware of what Web APIs there are. Going to put an effort to learning more of these things and getting comfortable with web APIs like Intersection observers and setting it all up with refs and callbacks
There is one serious situation custom hooks can land into is when the arguments change, the useEffect inside hook is not called synchoronously, in fact it is called asynchronously whenever React wants, therefore, the very first render after the change of the arguments, hook will still return the stale data (in this case the books because of useState). I land into this issue when I was creating my useLocalStorage which takes a key. And when I change the key it still returns data for the old key. This scenario is well taken care by useSWR hook, the moment the API URL changes the data returned is different. Can you make a video regarding these advanced patterns in REACT sometime?. That would be wonderful!
its totally amazing. i dont know about intersection observer so was a bit confused there but the video was mind blowing. Thanks for explaining the idea behind the infinite scroll
Awesome tutorial mate! I suggest including "Custom React Hooks" in your title. I was actually pleasantly surprised that this tutorial was going to include custom hooks. If I had saw that in the title, I would have clicked on it way earlier since React Hooks is the hot thing that everyone should be learning now. Furthermore, now that I've saved this to my React playlist, I still won't know that it includes custom hooks when I scan through all the video titles.
Using the ref on the children will force them to re-render when they're not the last item in the array, so maybe is better to use a the ref on a footer or something to observe the IntersectionObserver. And use useEffect to have the same functionality.
How to deal with the scenerio when each item has a delete button along side it and the user can delete item while scrolling, then data will change at the backend(The data will shift to previous page and I will not get the correct no of data for scrolled page ) I hope you understood what I mean to say
Nice tutorial. Although it's more correct semantically to use useEffect for attaching and disconnecting an observer on the last visible node rather than using useCallback like you did. Thanks for your videos!
Nice tutorial. This works smoothly for text based results. But it will struggle to render list of complex React components when list becomes huge. Can we also have a React window tutorial
Great video! I've been watching your React videos for some time now and was just wondering why you use es5 functions instead of es6 arrow functions? Again really good video!
It really depends on the use case. I find that if I am creating a named function such as function someName() {} then I use a normal function, but when I am nesting function calls in callbacks or making anonymous function calls like this someOtherFunction(() => {}) then I use an arrow function. It really depends, though, and for the most part I use arrow functions.
to be honest, I find the old school function() easier on the eyes. I only use => when doing anonymous functions and call backs like he said ^. But if it's just a function on the component, I like the look of the "es5" way.
Hi Kyle, thank you for sharing the video. 17: 05 to 17: 46 min saved me. I never used two userEffect before, one to clean the state another to fetch data until I watched your video. I am implementing Cursor relay pagination. I had an issue about clearing old data. Whenever react-route changes I could get old data and new data repeatedly. I 've fixed the issue after 2 days struggling with your help. God bless you brother.
Hey Kyle, thanks for the amazing tutorial, appreciate your work. I know this is an older video but had a quick question if you ever had the chance to read this, I can't figure out why the function inside the useCallback() where you defined the intersection observer get's called 4 times each time an intersection is observed. Best.
Its being called twice, the first time you feed the target (node ) to the observer and the second when the target intersects with its intersection root (the scrollable div container)
Great! I want to highlight that you keep adding new items to DOM, which will make DOM heavy. In this approach, We might have a large number of elements. How can we solve this issue? Is there any approach where we can maintain a specific set of items? No matter how long the list is.
Very good tutorial, but what if we don't use axios, instead we are using vanilla xmlhttprequest, how do we do throttling effect in this circumstances ?
![ทางเดินชีวิต - ธีเดช ทองอภิชาติ x อ.ไข่ มาลีฮวนน่า [Official MV]](http://i.ytimg.com/vi/1f3wcG16dd4/mqdefault.jpg)
Gotta say...this is probably the best, most straightforward tutorial I've ever seen!
why is openlibrary.org/search.json empty?
@@Mike37373 perhaps it needs params i.e.
axios({
method: 'GET',
url: url,
params: { q: query, page: pageNumber },
cancelToken: new axios.CancelToken(c => cancel = c)
}).then
i agree
Hey!, just a simple tip that i use, is when you want to know if an array have elements (means its length is greather than 0), you only have to put array.length instead of array.length > 0, because if array.length is 0, 0 means false, and if is not 0 so is true, sorry if my english is bad.
No need to apologize for your English. it was understandable.
Or you can just use the array, [] is falsy.
@@nishantmogha7679 array [] and {} are truthy brah
Also to make sure the app won't crash when array is null use optional chaining like myArr?.length
You can do that, but sometimes clearly code better than clever code
when i click this video, i only expect to know how to implement infinity scroll. But after 25 minutes i have learned way more than that, like custom hook. Thank you so much
I think this deserves a clarification - it's not just useCallback that can be assigned to an element's ref. Any function can be passed there, you just need to be very careful if the function updates state, since it can cause infinite re-renders.
Therefore, in this scenario, Kyle is right to use the useCallback hook, as the function he's using calls setPageNumber.
Let's say he used a plain function: the function he's using sets the state at some point, which re-renders the component. When the component gets re-rendered, the function gets reinstantiated. Since it's passed to an element's ref, the element gets re-rendered, which calls the function again. The function changes the state, causing the component to re-render... and we have ourselves an infinite loop.
Wonderful explanation!!
this literally just happened in class a few minutes ago in this example our TA was showing us...thank you now I understand why
Why can't we just create an reference using useRef and pass it to the component. Then Handel the intersection observer without a function.
Great explanation
Thanks for explaining that, this is the only section in the video that I needed more explanation on
awesome video. infinite scrolling starts at 17:50
That useCallback() behavior with useRef() that confused me, now I got it. Thank you Kyle, this is the best explanation about infinite scrolling with react 😍😍
Learned a lot from this. Thank you so much Kyle 🙏🏼
You're welcome!
I really have to say.. this was the best, clear, very staright forward tutorial. AWESOME
Great to see a video that includes some of the more advanced React features. I'll definitely need to watch this again, which is a feature of the best code run through videos.
Man I have watched literally thousands of paid courses, but no course matches the level of explanation that this guy provides. Simply Amazing. Hats off!
Kyle, you are great. Never found a tutor explaining such complex topics so easily. 😊
Thank you so much! I was struggling with window object so long and finally your video helped me!
th-cam.com/video/c0nKjMnDfG4/w-d-xo.html&ab_channel=Front-EndHacks
Watch Infinite Scroll Video here in Hindi
just from this video I have learned so many things, mainly the useRef and useCallback. thankyou
Awesome tutorial man. Straight to the point and well explained. Got an infinite scroll up and working in my application no problem after watching this. Subscribed!
I'm tried to use infinite scrolling library but it not looking good.
Your video had save my life it working great and smooth, Thanks
Amazing! Thank you very much, I thought it would be harder to make something like this.
Also THANKS because I finally got how to make a custom hook, I was having some struggles to get it.
thanks!! used your pagination api with this, tweaked it a little as i'm using sequelize and it works great.
This is a great tutorial, straight to the point and clear. Thank you, Kyle!
Thank you for this tutorial! I got something similar workign, I just wanted the "isVisible" for one of my elements to show up.
I think this video is a little too long, and getting the custom hook created is a little bit of a side job for getting infinite scrolling, and I would have preferred just getting the "isVisible" working, and then going from there.
That being said, thanks for the info, your tutorials are always at a good pace, and I like that you've included the source code!
Thank you so much for this tutorial, it literally helped me pass in a interview test 👏
I am really impressed by this tutorial, it helped me a lot in my current react project, thank you!
Just a side note, you can also use Debounce Component to have delay when the user stops typing. Anyway, Great job! thanks for this!
Very true. For this small use case it isn't really a big deal, but in a larger application this could save a lot of performance. Thanks for the tip.
@@WebDevSimplified can you point me to some resource for this"debounce"? Thanks
@@ManishKarki you can search for react-debounce-input
@@ManishKarki Just do a Google search for React debounce. Essentially all it is, is delaying the axios request.
Really good approach, dude your video helped me a lot to finish my project at work, Thank you so much
Your tutorials are incredible! It's so much great information in such a concise presentation.
Thank you for making such an understandable and useful lessons! You're really great🙏💛
I. You are awesome. This video is amazing. You just went straight to the point and your language was very clear. Thanks for sharing this content.
Didn't realize so little code was required for this. I'm too used to using libraries and I'm not aware of what Web APIs there are. Going to put an effort to learning more of these things and getting comfortable with web APIs like Intersection observers and setting it all up with refs and callbacks
Thank you so much! None of the other solutions worked for me except this!
There is one serious situation custom hooks can land into is when the arguments change, the useEffect inside hook is not called synchoronously, in fact it is called asynchronously whenever React wants, therefore, the very first render after the change of the arguments, hook will still return the stale data (in this case the books because of useState). I land into this issue when I was creating my useLocalStorage which takes a key. And when I change the key it still returns data for the old key. This scenario is well taken care by useSWR hook, the moment the API URL changes the data returned is different. Can you make a video regarding these advanced patterns in REACT sometime?. That would be wonderful!
This react lecture is AMAZING... Thanks from Korea.
its totally amazing. i dont know about intersection observer so was a bit confused there but the video was mind blowing. Thanks for explaining the idea behind the infinite scroll
Intersection Observer is a bit complex, but it makes doing things like infinite scrolling so much easier.
@@WebDevSimplified yes.. absolutely correct
Thanks for the tutorial. This is probably the best, most straightforward tutorial
Awesome tutorial mate! I suggest including "Custom React Hooks" in your title. I was actually pleasantly surprised that this tutorial was going to include custom hooks. If I had saw that in the title, I would have clicked on it way earlier since React Hooks is the hot thing that everyone should be learning now. Furthermore, now that I've saved this to my React playlist, I still won't know that it includes custom hooks when I scan through all the video titles.
Amazing tutorial, as special the approach to trigger the axios function via IntersectionObserver instead of div.scrollHeight.
Using the ref on the children will force them to re-render when they're not the last item in the array, so maybe is better to use a the ref on a footer or something to observe the IntersectionObserver.
And use useEffect to have the same functionality.
Nice video, worked like a charm
Just used this at work. Thank you Kyle!
This tutorial is amazing! Thank you very much for making it simpler!
Amazing video. You have made a complex thing look so easy. Keep up the great work!!
Thank you!
th-cam.com/video/c0nKjMnDfG4/w-d-xo.html&ab_channel=Front-EndHacks
Watch Infinite Scroll Video here in Hindi
Never saw any better explaination than this, thank you ..
The best tutorial I've ever seen
your videos are awesome-- thank you!
also, happy new year
Great explanation! Thanks Kyle!
you've a better solution than using scroll position broo, good job!!
A very great tutorial man.
The intersectionObserver is awesome!! so much more practical!
Very good information, especially the part about using useCallback instead of ref. I was just wondering how to grab the last node.
Thanks for this man, exactly what I was looking for, now I can create what I wanted. THANKSSSSSSSSSSSSSS
Awesome. Just what I was looking for. I used it in photo grid and full screen view in my app. Thanks
how to prevent multiple axios requests on infinite scroll ?
Cool . Got my all doubt cleared. Nice work
Very very straightforward, keep the good work and thanks!
How to deal with the scenerio when each item has a delete button along side it and the user can delete item while scrolling, then data will change at the backend(The data will shift to previous page and I will not get the correct no of data for scrolled page ) I hope you understood what I mean to say
5:24 - use https if you have problems
Thank you for this amazing video! My project was a little different but I managed to make it work in a short amount of time.
th-cam.com/video/c0nKjMnDfG4/w-d-xo.html&ab_channel=Front-EndHacks
Watch Infinite Scroll Video here in Hindi
Thanks a lot Kyle. All of your videos are top notch..
Thanks man. A much needed tutorial for me...
This is so easy to use and does help a lot! Thank you for the video!
A react native tutorial on this would also be awesome. Currently building an app with native.
I don't like mobile development so there probably won't be much if any React Native on my channel.
Nice tutorial. Although it's more correct semantically to use useEffect for attaching and disconnecting an observer on the last visible node rather than using useCallback like you did. Thanks for your videos!
Is there a difference though. Ive doing it the useEffect way but wonder if 2 methods differ in any way
Can you provide more details why ?
Really good content kyle, please make video on lazy loading and interceptor in react (:
Nice tutorial. This works smoothly for text based results. But it will struggle to render list of complex React components when list becomes huge. Can we also have a React window tutorial
what do you mean by that?
Thank man!! It was very simple to implement and add to the project.
Thanks a lot for the video🙏. Finally understood infinite scrolling.👍
I learned a lot from this video. Thank you, Kyle.
You are very welcome
Awesome tutorial!! thanks for this high quality work!
Very clever implementation!
Nice and clean tutorial! Very good explained!
Thanks for the great content!
Great video! I've been watching your React videos for some time now and was just wondering why you use es5 functions instead of es6 arrow functions? Again really good video!
It really depends on the use case. I find that if I am creating a named function such as
function someName() {}
then I use a normal function, but when I am nesting function calls in callbacks or making anonymous function calls like this
someOtherFunction(() => {})
then I use an arrow function. It really depends, though, and for the most part I use arrow functions.
to be honest, I find the old school function() easier on the eyes. I only use => when doing anonymous functions and call backs like he said ^. But if it's just a function on the component, I like the look of the "es5" way.
incredible bro i appreciate this🙌 kind of content
Very simple explanation. thanks alot
nice tutorial , clear explanation , thanks bro
Great Tutorial... Helped a lot
Wow, infinite scrolling was simplified many thanks, your explanations help me grok
Hi Kyle, thank you for sharing the video. 17: 05 to 17: 46 min saved me. I never used two userEffect before, one to clean the state another to fetch data until I watched your video.
I am implementing Cursor relay pagination. I had an issue about clearing old data. Whenever react-route changes I could get old data and new data repeatedly. I 've fixed the issue after 2 days struggling with your help.
God bless you brother.
why is openlibrary.org/search.json empty?
thanks, great tutorial. prob one of the best i ever watch
Thank you so much, useful❤
so much useful info in 25 mins 😄 thanks!
Really appreciate your work, simplest of all
th-cam.com/video/c0nKjMnDfG4/w-d-xo.html&ab_channel=Front-EndHacks
Watch Infinite Scroll Video here in Hindi
wow you just taught us to make a node_module. Thank you so much
Hey Kyle, thanks for the amazing tutorial, appreciate your work. I know this is an older video but had a quick question if you ever had the chance to read this, I can't figure out why the function inside the useCallback() where you defined the intersection observer get's called 4 times each time an intersection is observed. Best.
Its being called twice, the first time you feed the target (node ) to the observer and the second when the target intersects with its intersection root (the scrollable div container)
Great! I want to highlight that you keep adding new items to DOM, which will make DOM heavy. In this approach, We might have a large number of elements. How can we solve this issue? Is there any approach where we can maintain a specific set of items? No matter how long the list is.
24k pure gold. Thank you so much!
This is very helpful. Thank you.
thanks bro, very useful :)
Awesome explanation 👌🤩
This is a great example - thanks
You Solved My Problem Thanks Sir
Magnificent video 👏👏👏
When should this infinite scroll be used vs manual pagination?
Litterally you have an example on TH-cam check your notification bell
Very Useful Thank you saved my day
Nailed it. Thanks for the Topic
Learned a lot! Thanks
Love Your Videos bro 👏👏
1000 likes from my side, Brother.
Very good tutorial, but what if we don't use axios, instead we are using vanilla xmlhttprequest, how do we do throttling effect in this circumstances ?
With typescript your example doesn't work
thanks dude, u save my job. button like for u
Hey,why do we need to store previous books initially while just fetching all the books according to the string?
The best tutorial in youtube!!!