Next.js renders server component twice even with ReactStrictMode disabled — still happens in production Help #78556
Replies: 2 comments 3 replies
-
So I’m using client components across the board, including in page.tsx. I get that skipping Server Components can cause double API calls because of client-side hydration — that part makes sense. But hear me out: even components that don’t fetch data (like buttons and inputs) are rendering twice. That’s what made me think this isn’t just about API calls. It seems like React’s hydration behavior and how it handles effects on the initial load is playing a big role here too. Curious if anyone else has run into this or has thoughts on what’s really going on behind the scenes? |
Beta Was this translation helpful? Give feedback.
-
Hi, You can do: npx react-scan@latest https://vras-ai-theanurags-projects.vercel.app/ And that'll help you identify the issue. I think, it can be related to ThemeProviders, or Auth Providers in your app. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I'm seeing my page render twice even after turning off ReactStrictMode.
The component uses \useEffect
to fetch images from the backend. This still happens in production (Vercel deployed).
Is this normal in RSC/Next 13+? Or am I missing a fix?
Here's the repo: github
live link: https://vras-ai-theanurags-projects.vercel.app/
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions