Error in published TypeScript definitions about react-error-boundary HOT 4 CLOSED

Fix published in 4.0.2

Thanks for the helpful bug report!

from react-error-boundary.

This looks like a ParcelJS bug (maybe in @parcel/packager-ts?)

I think that line should be:

- render(): import("react").FunctionComponentElement<import("react").ProviderProps<import("ErrorBoundaryContext").ErrorBoundaryContextType | null>>;
+ render(): import("react").FunctionComponentElement<import("react").ProviderProps<ErrorBoundaryContextType | null>>;

There's no reason to "import" the ErrorBoundaryContext when it's already declared in the d.ts file within scope.

from react-error-boundary.

I filed a Parcel bug with repro at parcel-bundler/parcel#8908

from react-error-boundary.

Confirmed a workaround in my test project:
Note that a workaround for this issue seems to be declaring an explicit return type:

return createElement(
  ErrorBoundaryContext.Provider,
  {
    value: {},
  },
  children
) as ReactElement;

// dist/index.d.ts
export class ErrorBoundary extends Component<PropsWithChildren> {
    render(): ReactElement<any, string | import("react").JSXElementConstructor<any>>;
}

from react-error-boundary.