What problem does this feature solve?

Below is from React Server Component RFC

Ultimately, we realized that neither pure server rendering or pure client rendering were sufficient. Server rendering allows applications to easily access server-side data sources and to quickly show static content, while client rendering is critical for rich, interactive features where users expect immediate feedback. But mixing server and client rendering often means mixing technologies: writing code in two languages, using two frameworks, keeping two sets of idioms and ecosystems in mind. It also means dealing with cross-language data transfer and often requires duplicating logic, once for server-rendered views and once for interactive client previews.

Server components allow React apps to get the best of both server and client rendering while using a single language, a single framework, and a cohesive set of APIs and idioms. We are still exploring the full design space of Server Components, but we have shipped our first production integration and are actively exploring some additional open areas of research. The high-level design of Server Components is described below.

It's an addition to SSR and it's a nice idea to make full use of the server in front-end rendering.

If we apply this idea to Vue, due to the templates, the server components can be optimized to gain better performance.

Vue 3 has already made efforts for supporting SSR, will things like React Server Component also be considered?

What does the proposed API look like?

support for server component. and libraries providing APIs in composable form for network, file system, databases, etc.

This should go as an RFC: https://github.com/vuejs/rfcs