Content pfp
Content
@
0 reply
0 recast
0 reaction

dylan pfp
dylan
@dylsteck.eth
some things that have been making nextjs faster/cheaper for me lately: - prefetch your links with their <Link> - don’t use their <Image>, use <img> + a CDN(I like Cloudinary) - if you use RSCs you need to use suspense and proper data loading patterns(and caching) otherwise your app becomes sooo slow - keeping certain values either strictly static or on the client
3 replies
2 recasts
12 reactions

dylan pfp
dylan
@dylsteck.eth
anything I’m missing? also I feel like a lot of this just comes down to general best practices
3 replies
0 recast
0 reaction

dylan pfp
dylan
@dylsteck.eth
*also* just waiting for those turbopack-enabled builds someday, still crazy to me sometimes that I’m waiting like 2-3 mins for a nextjs build on vercel lol
0 reply
0 recast
0 reaction

pugson pfp
pugson
@pugson
you can still fetch data on the client where it makes sense
0 reply
0 recast
0 reaction

Tiago pfp
Tiago
@alvesjtiago.eth
for "feeling faster" optimistic updates (either through useOptimistic or custom implementation)
0 reply
0 recast
0 reaction