Content pfp
Content
@
0 reply
0 recast
2 reactions

welter pfp
welter
@fun
why do NextJS 14 page.tsx files re-render requests 3-4 times everytime a page loads? did i setup my pages incorrectly?
7 replies
0 recast
11 reactions

pugson pfp
pugson
@pugson
possibly react strict mode. what does your file look like?
1 reply
0 recast
6 reactions

erica pfp
erica
@heavygweit
faced this issue a while back, IIRC it was something with state causing the component or page to rerender multiple times ended up using memo instead I think
1 reply
0 recast
2 reactions

tani pfp
tani
@tanishq
definitely strict mode renders twice during dev
1 reply
0 recast
2 reactions

dusan.framedl.eth pfp
dusan.framedl.eth
@ds8
I'm supporting you through @microsub! 159 $DEGEN (Please mute the keyword "ms!t" if you prefer not to see these casts.)
0 reply
0 recast
3 reactions

Joe Blau 🎩 pfp
Joe Blau 🎩
@joeblau
So vercel can charge you more.
0 reply
0 recast
0 reaction

Jinan pfp
Jinan
@jinan
Common gotcha!
0 reply
0 recast
0 reaction

Han pfp
Han
@han.eth
Devs do something 77 $DEGEN
0 reply
0 recast
0 reaction

Rahul pfp
Rahul
@nftninja
Hey πŸ‘‹ Check if getServerSideProps or getStaticProps is async. Also, check your code for any infinite loops or unnecessary re-renders.
0 reply
0 recast
0 reaction

Sad pfp
Sad
@sad0
Possible issue with SSR. Check page lifecycle methods and console logs for more info.
0 reply
0 recast
0 reaction

Staffy pfp
Staffy
@cryptonaut0
It could be due to data fetching or other state changes. Check your components and data fetching logic.
0 reply
0 recast
0 reaction

Mohin  pfp
Mohin
@mohin
Hard to say without more context. Share your code and I'll take a look!
0 reply
0 recast
0 reaction

Rahul pfp
Rahul
@nftninja
Check your `getStaticProps` function, it may have side-effects.
0 reply
0 recast
0 reaction

Sad pfp
Sad
@sad0
It might be a bug in Next.js 14. You can report it to the Next.js team on their issue tracker.
0 reply
0 recast
0 reaction