-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
React Router Framework on Netlify #16186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@chargome thanks for checking it! As a workaround, I added this to the [functions]
included_files = ["instrument.server.mjs"] And also needed to add this environment variable to Netlify: If you find a way to add Sentry to the server without the |
@cjoecker thanks for the hint!
Yes this is generally a pain point with ESM frameworks, if for example you just import the instrumentation file first you will get incomplete instrumentation – which is why we need to rely on the |
@chargome, the workaround I thought would work on Netlify, is not working after it is deployed on production. I opened this support ticket on Netlify, but with the current Sentry setup for React Router, it cannot be deployed there. |
@cjoecker you can still import the instrument file on the top of your |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/react-router
SDK Version
9.15.0
Framework Version
No response
Link to Sentry event
7.5.0
Reproduction Example/SDK Setup
No response
Steps to Reproduce
Expected Result
Actual Result
I guess the
instrument.server.mjs
cannot be started on Netlify functionsThe text was updated successfully, but these errors were encountered: