createResource swallows error?
I noticed errors get swallowed when I use
createResource
. Here is some simplified example code:
The error is not logged in the console9 Replies
it is caught by the nearest error boundary
I attached those event listeners before the call:
If the promise rejection is unhandled, it should call
'unhandledrejection'
afaik but it doesn't.no I meant literally an ErrorBoundary
actually the app didnt render yet at this place hm. but why would that matter @lxsmnsyc
in any case I dont see why the error would be swallowed if I have the
'unhandledrejection'
handler.well you didn't say where the createResource was constructed 🤷♂️
but does it matter as long as I have a
'unhandledrejection'
handler?createResource handles errors itself

the signal will have error set on error 😄
resource return