componentDidCatch doesn't work in React 16's renderToString

[aickin]

I tried out a simple test case for the new componentDidCatch error handling code in React 16 SSR with the following code:

import React from "react"
import { renderToString } from "react-dom/server"

class ErrorBoundary extends React.Component {
  constructor(props) {
    super(props);
    this.state = { hasError: false };
  }

  componentDidCatch(error, info) {
    // Display fallback UI
    console.log("componentDidCatch");
    this.setState({ hasError: true });
  }

  render() {
    if (this.state.hasError) {
      // You can render any custom fallback UI
      return <h1>Something went wrong.</h1>;
    }
    return this.props.children;
  }
}

class ThrowingComponent extends React.Component {
  render() {
    throw new Error("Ooooops");
  }
}

console.log(renderToString(<ErrorBoundary><ThrowingComponent/></ErrorBoundary>));

and the result with 16.0.0-beta.5 was:

/Users/.../throwingimpl.js:68
      throw new Error("Ooooops");
      ^

Error: Ooooops
    at ThrowingComponent.render (/Users/.../throwingimpl.js:27:11)
    at resolve (/Users/.../node_modules/react-dom/cjs/react-dom-server.node.development.js:1891:18)
    at ReactDOMServerRenderer.render (/Users/.../node_modules/react-dom/cjs/react-dom-server.node.development.js:1988:22)
    at ReactDOMServerRenderer.read (/Users/.../node_modules/react-dom/cjs/react-dom-server.node.development.js:1964:19)
    at renderToString (/Users/.../node_modules/react-dom/cjs/react-dom-server.node.development.js:2234:25)
    at Object.<anonymous> (/Users/.../throwingimpl.js:31:13)
    at Module._compile (module.js:569:30)
    at loader (/Users/.../node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/.../node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:503:32)

As far as I can tell, this code should not throw but should rather output <h1>Something went wrong.</h1>.

I'm afraid that maybe we didn't add componentDidCatch to the new server renderer.

[sophiebits]

This is intentional / a known limitation. With streaming rendering it's impossible to "call back" markup that has already been sent, and we opted to keep renderToString and renderToNodeStream's output identical.

@sebmarkbage has ideas about how we could potentially support something along these lines one day if we have a small client runtime (ex: outputting script tags that remove previously-sent content).

[sebmarkbage]

That's intentional. The next next out-of-order server renderer will have error boundaries. But it doesn't really make sense on an in-order streaming server rendering. Since we could've already flushed the boundary. We could buffer inside error boundaries but that would mean that we don't actually do any streaming rendering since the best practice is to have an error boundary at the root.

We could support this in the renderToString API but that's easy-ish to implement yourself around it so not high pri and would likely go into the work of the out-of-order renderer.

[aickin]

Ah, got it. My fault! ;) Thanks, and closing this issue.

[asmagin]

This looks like a dirty but a much needed hack to overcome the intentional limitation: https://github.com/doochik/babel-plugin-transform-react-ssr-try-catch

Would be nice to have something like that built-in.

[zekchan]

In your case you can use https://github.com/zekchan/react-ssr-error-boundary - it is component using renderToStaticMarkup on server for render your component

[asmagin]

renderToStaticMarkup() is not the same as renderToString(), as it is not rendering React attributes and markup won't be resolved on client-side.

Anyway, I solved it already by inheriting SafePureComponent from PureComponent and implementing error catching in its render().
The implementation of render() is calling safeRender(), which is wrapped in try/catch and implemented in all components derived from SafePureComponent.

[zekchan]

Workaround with try-catch'ing render method will help you only if error throw in that render method. But if error occurs deep in react tree it will not.
renderToString() method in react 16 render only one special attribute - data-reactroot

[asmagin]

It is true, that's why I'm creation all components from SafePureComponent.
Also the root cause of the problem is streaming that in React16 used for renderToStaticMarkup() as well (by the moment your error happened, part of the component is sent already)

[japesh]

try-catch'ing the renderToString method can also be helpful at server side as mentioned in following issue #3730

[abhirajambasta]

try https://www.npmjs.com/package/react-isomorphic-error-boundary. This helps a lot.

[mwamedacen]

Thank you @abhirajambasta for react-isomorphic-error-boundary package. However there's a limitation to it (see nayaknotnull/react-isomorphic-error-boundary#6).

Any update about this subject please ?