@shelton-xiaoteng-ma is attempting to deploy a commit to the timlrx's projects Team on Vercel.

A member of the Team first needs to authorize it.

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Thanks, this closes #869

There's a small bug introduced with the change - could you help to resolve it? The main tags page still shows the "Next" button as active despite it being the last page: https://tailwind-nextjs-starter-blog-git-fork-s-a5ce5a-timlrxs-projects.vercel.app/blog?page=2

Ok, I have solved it.
This bug is caused by using the same ListLayout from @/layouts/ListLayoutWithTags, now I have refactored /blog, deleted /blog/[page]/page.tsx, and made sure /blog and /tags/next-js uses the same pagination logic

Thanks, the not found logic seems to be different. For e.g. https://tailwind-nextjs-starter-blog-cxns6sbn4-timlrxs-projects.vercel.app/blog?page=3 directs to page 1 despite there not being a valid page 3. It displays a 404 error for the tag routes.

The URL you are using is outdated, I saw the new deployment URL: https://tailwind-nextjs-starter-blog-nvzeomgx1-timlrxs-projects.vercel.app/, so https://tailwind-nextjs-starter-blog-nvzeomgx1-timlrxs-projects.vercel.app/blog?page=3 shows Not Found as expected

Opps sorry, was looking at the old one. In that case the changes looks good to me and thanks for the contribution!

I get a bunch of build errors for the static version of the site:

Error occurred prerendering page "/tags/markdown". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Route /tags/[tag] with `dynamic = "error"` couldn't be rendered statically because it used `await searchParams`, `searchParams.then`, or similar. See more info here: https://nextjs.org/docs/app/building-your-application/rendering/static-and-dynamic#dynamic-rendering
Export encountered an error on /tags/[tag]/page: /tags/markdown, exiting the build.
Error occurred prerendering page "/tags/images". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Route /tags/[tag] with `dynamic = "error"` couldn't be rendered statically because it used `await searchParams`, `searchParams.then`, or similar. See more info here: https://nextjs.org/docs/app/building-your-application/rendering/static-and-dynamic#dynamic-rendering
Export encountered an error on /tags/[tag]/page: /tags/images, exiting the build.

I think the inclusion of searchParams changes it from statically rendered to dynamic rendering. Do you have any work arounds that would still allow it to be statically rendered?

Sorry for the new error. I am not familiar with this.
ChatGPT says that you can use "precompute all possible values", I think it works for tags, but for pages, Maybe Use useSearchParams and handle logic on the client.
I will try other options later.