[paulgb]

Nicely done!

Dumb question, but as someone who is aware of server components but hasn't used it, what makes a hook “server component safe”? I assume it doesn't necessarily mean that you can use it on the server (e.g. useMouse), but that if you use it it will not break server-side rendering or complain about a DOM diff?

[terandle]

Not a dumb question. I think calling any hooks server component safe is going to mislead and add confusion to a lot of developers for this very new tech. Hooks are not allowed in server components. This library is SSR safe which has been a concern since before server components were ever a thing.

[tylermcginnis]

Yeah it's [poor phrasing](https://twitter.com/tylermcginnis/status/1663648010558132224) on our part. How it's being interpreted vs how I thought it would be interpreted are different. We'll update it.

[technion]

I don't blame you for this. The React team recently talking about "React Server Components" as though most React users are running it on NodeJS backends and introducing magic "use client" strings is putting everyone in a confused position and I don't think there's a good phrasing for you.

[egeozcan]

Something like "compatible for server-side rendering in non react server components" :)

And people suggest juniors to start on the front-end because it's less complicated...

[5Qn8mNbc2FNCiVV]

I've read "Server component safe" and thought that doesn't make sense from the get go. It's 100% only bad communication here