Uh oh!
There was an error while loading. Please reload this page.
feat(sveltekit): Introduce client-side handleError wrapper - #7406
Conversation
size-limit report 📦
|
Uh oh!
There was an error while loading. Please reload this page.
Lms24
left a comment
There was a problem hiding this comment.
Nice, looks great! Let's just make sure that the conditional export paths are fine in the tarball, then this is good to 🚀
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
5e04be9 to
2a9e94bComparepsytrx
commented
Mar 10, 2023
Currently, This would allow us to filter out, transform and enrich errors in an idiomatic way. exportconsthandleError=sequence(filterUselessErrors,addContextOrMetadata,sentryHandleError,myCustomHandleError);Would it make sense for you to suggest such a change to the SvelteKit team? I'm open to starting a discussion. I'm not quite sure about the consequences, but it feels like it should be a non-breaking change. |
Lms24
commented
Mar 10, 2023
@fjdumont thanks for the suggestion. We're definitely going to consider Feel free to go ahead and open a discussion on the SvelteKit repo 👍 |
ref #7402
Adds a wrapper for the client-side
handleErrorhook.Usage is like the following: