Comments on: Combining React Server Components with react-query for Easy Data Management

By: Adam Rackis

Adam Rackis — Mon, 05 May 2025 18:42:23 +0000

In reply to Naeem. It's been awhile, but it's usually best practice to start the fetch for data as high up as you can, and then await it as low as possible, so you minimize the risk of blocking things unnecessarily, while data are in flight.

By: Naeem

Naeem — Mon, 05 May 2025 18:33:34 +0000

I have checked the code. One question I have is, what is the point of adding the prefetchQuery for books-query in the page.tsx, which is a server component, and down the line doing the same books-query call in Books.tsx? Because, as per my understanding, it will fire the books api query twice, once from page.tsx and then from Books.tsx.

By: Adam Rackis

Adam Rackis — Mon, 02 Sep 2024 16:23:13 +0000

In reply to Jeff. Basically, when you call your api endpoints from the server, during ssr, no cookies will be included, since the request is happening in Node, as opposed to from the browser. To fix, you'd have to put all your cookies into React context, which introduces security concerns. The linked library allows you to do that, while encrypting them.

By: Jeff

Jeff — Mon, 02 Sep 2024 15:40:56 +0000

I don’t understand the update part about making the cookies available on SSR/CSR. is there a complete example somewhere on how one would implement this?

By: thankyou

thankyou — Mon, 17 Jun 2024 03:08:51 +0000

great article, i have a question
Nextjs app directory version’s client component is being rendered on server first(SSR). if i use useQuery inside client component does it fetch data is serverside?

By: Glody mbutwile

Glody mbutwile — Sat, 25 May 2024 03:24:05 +0000

Great article. RSC, routing is server-centric. So, client can’t “see” the next URL before the server responds.

I think as the windows.history won’t attempt to load this URL after a call to pushState() that is why it is not integrated with transitions