You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
@sentry/remix exports ErrorBoundary in its types but it is only present in the browser, not in node #16298
The ErrorBoundary component is available in both client and SSR contexts, the same as it was in Sentry 8.x
Actual Result
ErrorBoundary is not exported when you're in a node.js environment because of the different entrypoint, and so you fail in prod without a TypeScript error.
This is a pretty tricky way to handle typescript exports: I would sort of understand if there were entrypoints like @sentry/remix/client and @sentry/remix/node, but given that it's one package you import, the types are kind of "lying" about what's actually available: I write isomorphic code as if ErrorBoundary exists, but it only exists in one environment (the browser) and crashes the other (node).
Hi @tmcw, thanks for writing in. We're looking into why the export was removed. Indeed it wasn't called out in the migration to v9 so the removal was probably unintentional.
Activity
andreiborza commentedon May 15, 2025
Hi @tmcw, thanks for writing in. We're looking into why the export was removed. Indeed it wasn't called out in the migration to v9 so the removal was probably unintentional.
cc @onurtemizkan
fix(remix): Add missing `client` exports to `server` and `cloudflare`…
github-actions commentedon May 20, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #16341, which was included in the 9.21.0 release.