`captureException` is potentially `undefined`

[nathanbrachotte]

Hey there,
trying to implement captureException from useBaselimeRum.
This hooks return type is

{
    setUser: (userId?: string) => void;
    sendEvent: (message: string, data?: any) => void;
    config?: undefined;
    _trackWebVital?: undefined;
    captureException?: undefined; // undefined here
} | {
    config: BaselimeRumConfig;
    setUser: (userId?: string) => void;
    _trackWebVital: (metric: any) => void;
    captureException: (error: Error, info?: React$1.ErrorInfo) => Promise<void>;
    sendEvent: (message: string, data?: any) => void;
}

I'm curious to know in which context captureException would not be defined.

[Meags27]

I have the same issue, typescript throwing warnings that it could be undefined. "TS2722: Cannot invoke an object which is possibly undefined"

 catch (error) {
      setIsSending(false);
      if (error instanceof Error) {
        setErrorMessage(error.message);
        captureException(error);
      }
    }

[Ankcorn]

Hey,

captureException is undefined if you are using it outside of the BaselimeRumContext. It should probably just be a no-op in this scenario rather than undefined so I will fix that.

In the meantime you can call the method like this

captureException?.()

Which should hopefully silence your TS error

[Ankcorn]

Thank you @Meags27 and @nathanbrachotte. This is fixed in 0.2.9

Sorry its so late. I hope this helps