Reputation: 2510
What is the recommended approach to upload source maps to sentry from a next.js project
Summary:
- Hosting next.js application on Vercel
- Using sentry.io to monitor errors
- Trouble setting source maps up correctly
Long Form:
A lot has changed since the early releases of sentry (where the sdk was called raven). Also a lot has changed with next.js and generating source maps is internalized and can be configured in the next.config.js as can be read here.
I am wondering what the correct (best-practice) approach is for uploading/providing source maps to sentry when deploying an application on vercel and why.
We do have the sentry documentation here but this is a little light and feels fairly generic/not next.js specific.
I do get issue reports in sentry, but they do not appear to include stack traces or where the error was thrown in the code.
Upvotes: 5
Views: 3310
Answers (1)
Reputation: 3157
Sentry’s Vercel Integration connects your Sentry and Vercel projects to automatically upload source maps and notify Sentry of release deployment.
- https://github.com/vercel/next.js/tree/canary/examples/with-sentry
- https://vercel.com/integrations/sentry
- https://docs.sentry.io/product/integrations/deployment/vercel/
Upvotes: 1
Related Questions
- Next.js in Vercel with Sentry - ignore source maps in production
- How to setup source map on Sentry
- Artifacts not uploaded on Sentry on Vercel build
- NextJS - Sentry CLI Plugin: spawn ENOMEM
- Next.js source maps with typescript on Sentry
- Can not run server after add sentry to nextjs project
- How do I generate sourcemaps for nextjs?
- integrating Sentry in Next.js project
- Sentry: Upload sourcemaps from folder tree
- How to automatically create a Sentry release and upload source-maps to Sentry in a react project?