How To: Runtime exceptions in RemixJS actions and loaders? #17439
Unanswered
bzitzow-osh
asked this question in
Q&A
Replies: 1 comment
-
hey, you should not need to do any of that 😅 If you follow the whole manual setup here: And basically remove other things you are doing, then this should just work out of the box. Express is automatically handled through the remix SDK, no need to do any node/express specific stuff - just follow the remix SDK docs :) |
Beta Was this translation helpful? Give feedback.
0 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.
-
How To: Runtime exceptions in RemixJS actions and loaders?
RemixJS
Sentry
I've followed the instructions in the documentation Server-Side Performance Monitoring to use
withSentry()
to wrap theApp
component from the root loader.Scenario: Runtime exception is caught and sent to Sentry dashboard
Expectation
Would like this to work with Sentry.
Actual
This also confirms that the Sentry SDK is working.
app/entry.server.ts
app/root.tsx
server/index.ts
I've been searching for more information, and have come across various old ways of setting it up that seem to be deprecated:
wrapExpressCreateRequestHandler()
is deprecatedautoInstrumentRemix
config option is deprecated1. Should this "just work"?
2. Do I need to follow instructions for sentry + expressJS initialization to get support for runtime errors in RemixJS loaders and actions?
3. What am I missing?
Beta Was this translation helpful? Give feedback.
All reactions