React Server Components overview

Hydrogen is modelled after React Server Components, an approach that offers an opinionated data-fetching and rendering workflow for React apps. React Server Components are rendered in the server-side to improve the performance of React apps by decreasing bundle size and performing queries on the server.

This guide provides information about rules for server and client components and known limitations.

Component types

React Server Components include the following component types:

Type Description
Server Components that render on the server. Server components don't include any client-side interactivity. Only server components can make calls to the Storefront API.
Client Components that render on the client. These components include client-side interactivity.
Shared Components that render on both the server and the client.

Rules for server and client components

React Server Components have the following constraints on server and client components:

  • Component filenames ending with .client.jsx render on the client.
  • Component filenames ending with .server.jsx render on the server, and their dependencies aren't in the client bundle.
  • Component filenames not ending in .client.jsx or .server.jsx render on both the server and the client.
  • Client components can’t access server-only features, like the filesystem, and can only import other client components.
  • Server components can’t access client-only features, like state.

Due to these constraints, there are specific rules you need to follow when building your Hydrogen app.

A diagram that illustrates the rules that apply to server and client components


The following example shows a server component (Product.server.jsx) that uses the useShopQuery hook to fetch data. The data is passed to a client component (WishListButton.client.jsx) that uses state:

Sharing code between server and client

In addition to server-specific and client-specific components, you can also create components, hooks, and utilities that work on both the server and the client. This allows logic to be shared across environments, as long as the components, hooks, and utilities meet all the constraints of both the server and client components.

A diagram that illustrates server-specific and client-specific components and hooks, and shared components and hooks between the client and server

Although shared components have the most restrictions, many components already obey these rules and can be used across the server and client without modification. For example, many components transform some props based on certain conditions, without using state or loading additional data. This is why shared components are the default and don’t have a special file extension.

Known limitations

When you send props to client components from a server component, make sure that the props are JSON-serializable. For example, functions or callbacks can't be passed as props.

The following prop would send successfully:

The following prop wouldn't send successfully:

Next steps