This repository was archived by the owner on Oct 13, 2026. It is now read-only.
Repository navigation
Replies: 1 comment 2 replies
|
Caught exceptions can't be captured automatically. That's the whole point of catching them. You need to manually report them using Alternatively you can redesign your app so that the route handlers don't catch anything itself and then you add a global error handler as a last route that captures the exception and sends a 500 response. Then you would only need to capture in one place. Or if you don't want control over what is sent in the response then just don't try/catch exceptions and don't add an error handler. Then Sentry will capture those automatically and your app will respond with a generic 500 error. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi I'm seeing Sentry send uncaught errors but nothing found within a try-catch block. I read this earlier question and wanted to see if my setup might be preventing Sentry from sending the errors over. Thanks in advance!
server/index.js (entrypoint)
routers.js
MySpace.js
nuxt.config.js
All reactions