@DanielGiljam Thank you for submitting an issue!

Related: https://ivicabatinic.from.hr/posts/multipart-namespace-components-addressing-rsc-and-dot-notation-issues

Thank you for the report!

To explain why this is the case: when a server component imports a client component, it receives a special client reference that the RSC runtime knows how to send to the browser. In other words, you aren't receiving the underlying export, it's only used to be passed to the client.

This is described a bit here: https://react.dev/reference/rsc/use-client:

When a server evaluated module imports values from a 'use client' module, the values must either be a React component or supported serializable prop values to be passed to a Client Component. Any other use case will throw an exception

However, I think the error itself can be improved here. React actually has a special message for this case which should read something like:

Error: Cannot access on the server. You cannot dot into a client module from a server component. You can only pass the imported name through.

We will investigate why it's not being shown in this particular case.

As mentioned in #76000, there are numerous issues on the topic, and yet, we keep spending hours figuring out this ambiguous error. It's been like ages, and it really is disappointing. @ztanner