No only Error for FallbackProps

I’m using React-query, and we can type our error. But there is a conflit with react-error-boundary since the type is not an Error type, but a custom. How can we deal with that ?

• react-error-boundary version: 3.1.0
• node version: 12.19.1
• npm version: 6.14.10

Relevant code or config

const OrderDetailsViews = (
  props: RouteComponentProps<TParams>
): React.ReactElement => {
  const { match } = props
  const { t } = useTranslation()
  const orderId = Number(match.params.id)
  const handleError = useErrorHandler()

  const { data: order, error, refetch: refetchOrders } = useQuery<
    FindOneOrder,
    ApiError
  >(['order-details', orderId], () => api.orders.findOneComplete(orderId), {
    onError: err => handleError(err) <-- ERROR TYPE
  })
}

Suggested solution: We can pass our type like : handleError<ApiError>(err)

OR

interface FallbackProps<T extends Error> { <-- We can pass something else
    error: T;
    resetErrorBoundary: (...args: Array<unknown>) => void;
}

[kentcdodds]

And I would consider this a bug fix

[tommarien]

What is the need for it to be an error ? and not unknown like in node?

try {} catch(e: unknown){}

Also see #36 and #25