I have a Next.js application deployed on Vercel, and I’m facing issues with calling internal APIs that are protected with authentication(auth.js). In development and a custom build, I successfully used the token from the cookie and passed it as a cookie in the header. However, this method doesn’t work in production on Vercel.

I’m trying to understand how revalidateTag work. I’m used to Tanstack, where you from anywhere in the application can invalidate a cache and tanstack will refresh data associated with that tag. I’m using revalidateTag in the same manor and it works locally is I thought.
But when I deploy the application it does not work as I think, it returns initalData no matter what.

i am currently building a dashboard using nextjs language. this code is also connected to a test server database (currently local. i took a copy of the test server).

In my Nextjs Project I have the /search route with dynamic params like this search/[...catType]

i am building a next js application and for my site, query params are important and they need to be forwarded between pages back and forth. Below are the scenarios –

I have a user page, the structure looks like this: folder [id]: