😲 I Was WRONG About Next.js Client Components

Показать описание

#nextjs #nextjs13 #reaction

👇 Follow Me On Social Media:

Рекомендации по теме

Комментарии

Thanks for the crystal clear and fluid explanation

lifealliancegroup

The Title definetly gave me a mini heart attack, you definetly aren't wrong, its just a mishap in understanding. Your Next 13 playlist definetly taught me well.

fallen_turbo

I was wrestling with this exact paradox this week. Thank you!

funkdefied

What if you pass a ServerComponent as a prop other than children? Will it still be a server component?

snivels

So if i use import statement in a use-client component, it'll be a child of comp and rendered on client.
But if i pass it as prop, it's a server components? That's cool, I'm just blurred a lil about that

royal-thunder

What if I wrapped all my components with Context React >> Client Component ? Will all the children(and in this case all components) be clients components

slahomar

I might need practical examples. If theres a form filled by server props then it could be passed to client and i could modify it changing nothing from the server. Is that right? Might need correction..

rifwann

thx for video!

which means,

if i import server component in client component, it will be treated as client component

but if i give server component as prop to client component, it will be still server component

am i right?

김규화-ju

It says Server and Client _modules_, not Server and Client _components_. Quite a distinction. Modules boundaries are defined as files en ES Modules (and in turn by Next.js)

The key word is _modules_.

dealloc