Pagination In Server Components - Next.JS 14 Full Stack Real Project - Part 8

In This video you will learn how to implement pagination in server components of Next.js 14
✅ Episode 1: • Real Estate App with N...
✅ Episode 2: • NextJS 14 Full Stack |...
✅ Episode 3: • Next.JS 14 Full Stack ...
✅ Episode 4: • Authentication and Aut...
✅ Episode 5: • Delete Property and us...
✅ Episode 6: • Parallel And Intercept...
✅ Episode 7: • Landing Page -- Next.J...
✅ Episode 8 : • Pagination In Server C...
✅ Episode 9 : • Search Bar With useDeb...
✅ Episode 10 : • Stripe Online Payments...
GitHub Repo(Please give it a ⭐ on GitHub): github.com/vah....

[@innocentinnox]

great explanation

[@SakuraDev]

Thanks a lot

[@MolamikeDevs]

Thank you so much for your effort.

[@SakuraDev]

Thanks for your support 🙏

[@prashlovessamosa]

Thanks Sakura

[@SakuraDev]

Thanks a lot Prashant 🙏

[@SakuraDev]

Thanks a lot Prashant

[@starrynight72]

at 9:20 it says when users click the second page of pagination, the page param will be number one. But at 13:36, when you click page 2 of pagination, the pagenum value of the URL searchParam turns to be 2 which is different from what you said at 9:20. This confuses me a bit. And I think maybe the pagenum starts from 1 would be better, right?

[@SakuraDev]

Thank you for pointing that out! It seems there was a mix-up. The page parameter should indeed start from 1 for consistency. I'll make a note to correct this in the video description. Thanks for your attention to detail!