KIPRI
@kipri.dev
I wore mine so much that it got sun burned so YES, please! 🚀
November 12, 2024 at 5:58 AM
I wore mine so much that it got sun burned so YES, please! 🚀
Actually …where “that” is undefined… sorry.
November 9, 2024 at 8:02 AM
Actually …where “that” is undefined… sorry.
I did some digging. I think a combination of “unhandledrejection” and “error” event listeneres combined with “react-error-boundary” should do the trick, but it feels so bad…
November 9, 2024 at 7:13 AM
I did some digging. I think a combination of “unhandledrejection” and “error” event listeneres combined with “react-error-boundary” should do the trick, but it feels so bad…
Well yes, but what about errors that you might not know can happen in this wonderful, God’s language that is JS?
Lets say a fauly data model, e.g this.that.foo where foo is undefined? Those errors will still not get caught by any ErrorBoundary.
Lets say a fauly data model, e.g this.that.foo where foo is undefined? Those errors will still not get caught by any ErrorBoundary.
November 9, 2024 at 6:22 AM
Well yes, but what about errors that you might not know can happen in this wonderful, God’s language that is JS?
Lets say a fauly data model, e.g this.that.foo where foo is undefined? Those errors will still not get caught by any ErrorBoundary.
Lets say a fauly data model, e.g this.that.foo where foo is undefined? Those errors will still not get caught by any ErrorBoundary.
What are you using for error boundaries and are they catching all possible errors? I can’t seem to find anything that just works.
November 8, 2024 at 4:31 PM
What are you using for error boundaries and are they catching all possible errors? I can’t seem to find anything that just works.