`nextjs` vs `serverless` for Vercel deploy

[mikestopcontinues]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• N/A - Provide a link to the affected event from your Sentry account

Description

Vercel deploys to AWS lambda, so the nextjs package doesn't seem like the right fit, at least on the server-side. But outright replacing it in sentry.server.config.js doesn't seem like the right call either, as both nextjs/src/index.server.ts and the AWSLambda have custom initialization config (and neither export the components).

What's the right direction here? Thanks!

[mikestopcontinues]

I see there's something related going on in #3462. I should specify though that I'm also concerned about enabling tracing, which is supported by the serverless package, but not by nextjs.

[HazAT]

Hey, we tried to use the serverless SDK for tracking API routes, it generally works but doesn't bring a lot of benefits since Vercel is changing the default things that AWS exposes. So compared if you run it manually on AWS you don't get any additional info.

Instead, please upgrade to 6.3.4 and wrap you API routes like this:

import * as Sentry from '@sentry/nextjs';

const handler = async (req, res) => {
  throw new Error('API Test 4')
  res.status(200).json({ name: 'John Doe' })
}

export default Sentry.withSentry(handler);

Then we capture all errors.

[mikestopcontinues]

Thanks!