Is it okay to use `CatchBoundary` component as a generic error boundary component? | TanStack | Page 1

calm kite Jul 30, 2025, 3:31 PM

#

Referring to https://tanstack.com/router/v1/docs/framework/react/api/router/catchBoundaryComponent

I'll eventually be setting up Sentry to use their error boundary in most cases, but for cases where I'm handling known errors, I was wondering if CatchBoundary is safe to use as opposed to using something like react-error-boundary

CatchBoundary component | TanStack Router React Docs

The CatchBoundary component is a component that catches errors thrown by its children, renders an error component and optionally calls the onCatch callback. It also accepts a getResetKey function that...

lusty mortar Aug 8, 2025, 1:00 AM

#

can you clarify what you mean by "safe to use"?

calm kite Aug 20, 2025, 5:53 PM

#

sorry - your reply got lost in my inbox 😅 by "safe" i mostly mean is it okay to use as a general purpose error boundary component, similar to what one might use react-error-boundary for?

lusty mortar Aug 20, 2025, 5:59 PM

#

no worries m8. looking at the source code it looks fairly similar to react-error-boundary. and it looks like it itself has nothing to do with routing, so I think it's good to use. (I use react-error-boundary myself but might switch to this, as I was unaware it existed.)

one thing to note though is you'll also want to use this component above your router too in the off-chance that the router itself has an error and bubbles up and is uncaught

#Is it okay to use `CatchBoundary` component as a generic error boundary component?