Repository files navigation

Native implementation of React's server-side rendering (SSR) and React Server Components (RSC) architecture for Reason.

Designed to be used withreason-react andMelange. Together it enables developers to write efficient React components using a single language, while target both native executable and JavaScript.

• Server-side rendering HTML withReactDOM.renderToString/ReactDOM.renderToStaticMarkup
• Server-side renderingstreaming HTML withReactDOM.renderToStream (similar to react@18renderToReadableStream)
• IncludesReact.Suspense andReact.use() implementations
• server-reason-react-ppx - A ppx transformation to support JSX on native
• Allreason-react interface is either implemented or stubbed (some of the methods, like React.useState need to be stubbed because they aren't used on the server!)
• React Server Components - A ReactServerDOM module for streaming RSC payload, an esbuild plugin to enhance the bundle with client-components mappings, a Dream middleware to serve the RSC endpoint and a dummy implementation of a router (stillwork in progress)

Warning: This repo contains a few parts that are considered experimental and there's no guarantee of stability. Most of the stable parts are used in production at ahrefs.com, app.ahrefs.com and wordcount.com. Check each module's documentation for more details.

There are plenty of motives for it, the main one is thatahrefs (the company I work for) needs it. We use OCaml for the backend and Reason (with React) for the frontend. We wanted to take advantage of the same features from React.js in the server as well.

Currently 100% of the public site (ahrefs.com), the shell part of the dashboard (app.ahrefs.com) andwordcount.com are rendered on the server withserver-reason-react.

What made us create this library was mostly:

• Use the same language (Reason) for both server and client
• Embrace server-client integrations such as type-safe routing, JSON decoding/encoding, sharing types and logic, while keep enjoying functional programming patterns
• Native performance is better than JavaScript performance (Node.js, Bun, Deno)
• Writing React from a different language than JavaScript, but still using the brilliant pieces from the ecosystem
• Exploration of OCaml effects and React
• Further exploration with OCaml multicore, direct-style and concurrency with React features such as async components, React.use or Suspense

Explained more about the motivation inthis blog post and also in my talk aboutUniversal react in OCaml at fun-ocaml 2024 andServer side rendering React natively with Reason at ReactAlicante 2023

Aside from the core (React,ReactDOM andReactServerDOM), server-reason-react repo contains some common melange libraries to ensure components are universal. Some of them are reimplementations in native of those libraries, and others are new implementations. Currently they are part of the repository, but eventually will be moved out to their own opam packages and repositories.

Thedocumentation site is generated with odoc and hosted on GitHub Pages.

Thedemo folder contains a bunch of demos under a server to showcases the usages ofserver-reason-react. Check theREADME for how to setup and run it.

DM me