type ErrorBoundaryPropsWithFallback allows fallback to be null about react-error-boundary

[bvaughn]

If you want to render null with the way the library currently works, I think you have to pass a component that renders null (e.g. () => null)

Presently null kind of acts like a passthrough (so you could use the boundary for e.g. logging only, using onError)

[adam-zhu]

For me, passing null doesn't function as a passthrough because any caught errors are bubbled up and break the app.

Looking at the code, this is expected:
https://github.com/bvaughn/react-error-boundary/blob/master/src/ErrorBoundary.ts#L87

    if (didCatch) {
      const props: FallbackProps = {
        error,
        resetErrorBoundary: this.resetErrorBoundary,
      };

      if (isValidElement(fallback)) {
        childToRender = fallback;
      } else if (typeof fallbackRender === "function") {
        childToRender = fallbackRender(props);
      } else if (FallbackComponent) {
        childToRender = createElement(FallbackComponent, props);
      } else {
        if (isDevelopment) {
          console.error(
            "react-error-boundary requires either a fallback, fallbackRender, or FallbackComponent prop"
          );
        }

        throw error;
      }
    }

[bvaughn]

Ah, yeah that makes sense I guess I was confusing React's undefined fallback prop.

I don't feel strongly about this (and probably also won't work on it)

[bvaughn]

4.0.12 will render null if you specify fallback={null}