fix(ErrorBoundary): reset when the thrown value is null

[hovelopin]

What

ErrorBoundary can't be reset — neither via resetErrorBoundary() nor via resetKeys — when the thrown value is null. Once the fallback is shown it stays there.

Why

Both reset paths check error !== null to decide whether the boundary is currently active:

// resetErrorBoundary
if (error !== null) { ... }

// componentDidUpdate
if (didCatch && prevState.error !== null && hasArrayChanged(...)) { ... }

When null is thrown, getDerivedStateFromError(null) produces { didCatch: true, error: null }, so both guards fail and onReset / setState(initialState) never run. useErrorBoundary().showBoundary(null) followed by resetBoundary() hits the same path.

Only null is affected — the comparison is strict, so undefined, 0, "" etc. reset correctly.

How

• Gate both paths on didCatch (and prevState.didCatch) instead of error !== null. The existing "skip the first componentDidUpdate after an error" behavior is preserved since prevState.didCatch is false on that call.
• Add two tests to the "thrown values" block covering reset via prop and via resetKeys after throwing null. Both fail on main and pass with this change.

The existing "should support thrown null or undefined values" test only covered rendering and onError, which is why this slipped through.

[vercel]

@hovelopin is attempting to deploy a commit to the Brian Vaughn's projects Team on Vercel.

A member of the Team first needs to authorize it.

[bvaughn]

👍🏼

[bvaughn]

react-error-boundary@6.1.4