SolidJS9mo ago

Where does <ErrorBoundary/> catch errors?

The docs example shows an error being caught at component creation which makes sense, but what about * createEffect() calls * onMount()/createRenderEffect() * JSX expressions * event handlers The react answer I think is that it wouldn't catch any of these cases, which seems less useful when the solid signal chains are doing all the computation
1 Reply
thetarnav9mo ago
ErrorBoundary uses context api to communicate so anywhere that ctx can be available will be caught by an error boundary afaik so out of your examples only event handlers won't work unles you use runWithOwner but ErrorBoundary is meant to catch "rendering errors", not subsequent ones for specific user actions, those are on you
Want results from more Discord servers?
Add your server
More Posts
Warning when modal uses stateI have created a context provider `ModalProvider` that is meant to display a modal whenever it's `viIs there a way to render a solid component to html string from the browser?I want to send raw html string to another service where it gets printed as a pdf. The renderToStringCRUD App - Suggestion for Utility FunctionalityHey there! I'm developing an app which contains mostly CRUD functionality using typescript + solid. cant set signal exported from a contextI've recreated a simple example based on my code: https://stackblitz.com/edit/solidjs-templates-dhbcError: Hydration MismatchHello, I have an error with one of my plugin. I have always an issue with Hydration MisMatch. Can soPrevent a route component from running before the old routes `onCleanup` runsWhen I move from one page to another with the router, the flow seems to be: on `PageA` -> trigger mError: Hydration Mismatch with component from node_modulesHello, I have an issue with Solid-Start Hydration process. Everything is described on the github isBundled package breaks when used in PRODI am working on a package which provides hooks and components to be used in a Solid app. The packageBug with `solid-js/store` and `solid-primitives/history`I ran into a bug and reproduced it in this stackblitz. For some reason with this configuration of thClicking browser's Back button from external site doesn't render the right state**The problem occurs only in production, not in localhost.** When a user is redirected to an extern