Hops React

hops-react works in tandem with hops-build and hops-config to make an integrated solution for universal ("isomorphic") rendering using React. It provides a minimal API and hides the tricky bits of setting up React for such use-cases.

Out of the box, hops-react additionally supports React Router and React Helmet.

Installation

npm install --save react react-dom react-helmet react-router react-router-dom hops-react hops-config

Basic API

render(reactElement, context)

render() is the main hops-react API. Its return value differs depending on the environment: in a browser context, it returns a plain function handling mounting of the app and hot module replacement. In a Node.js context, it returns an Express style middleware function. In both cases, its return value is meant to be the default export of your application's main entry file.

render() accepts two arguments: reactElement, your React application's root element, and context, an optional hops-react rendering context instance.

import React from 'react';
import { render, createContext } from 'hops-react';

const App = () => <h1>Hello World!</h1>;

export default render(<App />, createContext());

createContext(options)

createContext() generates a rendering context containing most of the actual implementation used by render. It takes a couple of options:

<Miss />, <Status code={200} /> and <Header name="x-foo" value="bar" />

To declaratively control server behavior from your application, you can use the React components provided by hops-react. Neither of these components produces any html output, they are effectively no-ops if used in the browser.

On the server, however, <Miss /> makes sure Express' next() middleware function is being called, signalling Express that your application is not responsible for handling the current request. <Status />, however controls the HTTP status code returned by the server.

<Header /> allows to set abritraty http headers for each request. Elements rendered more deeply will override those included higher up in the rendered tree. Adding the same header (such as Set-Cookie) multiple times can be achieved by providing an array as value. <Header name="x-foo" value={['bar', 'baz']}/>

Basic Example

import React from 'react';
import Helmet from 'react-helmet';
import { Route, Switch } from 'react-router-dom';
import { render, createContext, Miss } from 'hops-react';

import { headline } from './styles.css';
import { template } from './template.tpl';

const Home = () => (
  <div>
    <Helmet>
      <title>Example</title>
    </Helmet>
    <h1 className={headline}>Hello World!</h1>
  </div>
);

const App = () => (
  <Switch>
    <Route exact path="/" component={Home} />
    <Miss />
  </Switch>
);

export default render(<App />, createContext({ template }));

Render Contexts

Most of hops-react's functionality is implemented in a render context. You can either use one of the createContext factory functions provided by hops-react, hops-redux and hops-graphql or you can provide your own implementation. You can even mix-and-match default and custom context definitions.

hops-react does not use conventional JavaScript inheritance for its render contexts, but rather relies on mixinable to provide a form of multiple inheritance.

Composition API

combineContexts(...contextDefinition)

Calling combineContexts with one or more contextDefinitions creates a context factory function similar to the createContext function described above.

contextDefinitions can be constructor functions or prototype objects. Both are being used behind the scenes to instantiate specialized sub-contexts. All their methods that do not implement lifecycle hooks (see below) are private, as sub-context instances are hidden.

The sub-context instances are completely isolated and they cannot interfere with one another. Objects created with a createContext factory are essentially facades

ReactContext

hops-react exports its basic context definition as a constructor function to allow simple sub-classing and composition using combineContexts. For example, by extending it and overriding its enhanceElement method, you can very easily provide your own ReactRouter setup.

Lifecycle API

bootstrap()

The bootstrap lifecyle hook allows you to set up your application and perform data fetching or other asynchronous operations. You are expected to return a Promise - and the bootstrap operations from all active contextDefinitions are performed in parallel. Rendering is blocked until all Promises have been resolved (or rejected).

enhanceElement(reactElement)

By implementing enhanceElement, you can wrap your application's root element in additional, usually purely functional components such as Redux's or React-Intl's Providers. This way, you can keep the low-level (plumbing) parts of your application nicely separated from the high-level (porcellain) parts.

getTemplateData(templateData) (Node.js only)

getTemplateData is supposed to return an object that is being passed to the server-side template function. Please check out hops-react's default template to get an idea on what keys are supported.

templateData are being piped through the different implementations: make sure to extend or modify the object that is being passed into your implementation.

renderTemplate(templateData) (Node.js only)

renderTemplate is expected to be a rather simple, synchronous template function: data in, HTML string out. If you want to provide your own implementation, you might want to remember that hops-build-config allows you to simply require/import template files.

getMountpoint() (Browser only)

getMountpoint is meant to synchronously return the DOM-node your application is supposed to be mounted into.