Loading video...
Video Failed to Load
When to use Server vs Client components in Next.js 13
148,146 views • 2 years ago •via X (Twitter)
10 Comments

Great post! One Q: If my client component uses useSWR, is it possible to use a server component to avoid exposing my bearer token to the client? From the docs it seems useSWR is only available in client components

Since the latest release I noticed they’d made some huge performance improvements on moments. I’ve mostly always used my own time ago and date functions but might have to start using it again

Nice! The beauty of RSC is that it eliminates the concern of the client bundle size. It doesn't matter if the library is 2kb or 300kb if it stays on the server. So even if moment stayed large, it would be perfectly fine to use it on the server.

This is an extremely well-made video! Super succinct and straight to the point. Love it!

I think it's interesting that there's not much buzz around the fact that RSCs allow you to use "heavy" dependencies without increasing bundle size. Even though they were literally announced as "Zero-Bundle-Size React Server Components," it seems to be flying under the radar. Don't you think?

Yep. The common notion is that "RSC, generally, makes client bundle smaller," not "with RSC, you can safely pick heavy dependencies." The ideas are similar, but this particular angle is often under-appreciated.

Alex hit our brains again, thanks for this one

Worth a follow up on how server actions fit in the mix but this is a banger tweet as always @t3dotgg 👆👆👆

Are you doing that with Keynote? Great content and presentation, by the way.

Yep, Keynote. Thanks
Related Videos
How to use Next.js metadata if the page is a client component
Alex Sidorenko
91,579 views • 1 year ago
