Crash on server side running on Vercel after upgrading to Next.js 12

[davguij]

• 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
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other: @sentry/nextjs

Version:

6.13.3

Description

After upgrading a project from Next 11.1.2 to 12.0.1, the Next.js-powered API endpoints start to crash, as in https://drafted-webapp-hmopbeh9f-davidguijarro.vercel.app/api/status.

Here's a sample log of the error:

[GET] /api/status
09:32:11:52
2021-10-29T07:32:12.548Z	1c5c0769-4fd8-4480-8b9a-08598598cd1f	ERROR	Error: Cannot find module './browser'
Require stack:
- /var/task/node_modules/@sentry/tracing/dist/index.js
- /var/task/node_modules/@sentry/node/dist/handlers.js
- /var/task/node_modules/@sentry/node/dist/index.js
- /var/task/node_modules/@sentry/nextjs/dist/index.server.js
- /var/task/.next/server/pages/api/status.js
- /var/task/node_modules/next/dist/server/next-server.js
- /var/task/___next_launcher.js
- /var/runtime/UserFunction.js
- /var/runtime/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:889:15)
    at Function.Module._load (internal/modules/cjs/loader.js:745:27)
    at Module.require (internal/modules/cjs/loader.js:961:19)
    at require (internal/modules/cjs/helpers.js:92:18)
    at Object.<anonymous> (/var/task/node_modules/@sentry/tracing/dist/index.js:3:17)
    at Module._compile (internal/modules/cjs/loader.js:1072:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
    at Module.load (internal/modules/cjs/loader.js:937:32)
    at Function.Module._load (internal/modules/cjs/loader.js:778:12)
    at Module.require (internal/modules/cjs/loader.js:961:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/var/task/node_modules/@sentry/tracing/dist/index.js',
    '/var/task/node_modules/@sentry/node/dist/handlers.js',
    '/var/task/node_modules/@sentry/node/dist/index.js',
    '/var/task/node_modules/@sentry/nextjs/dist/index.server.js',
    '/var/task/.next/server/pages/api/status.js',
    '/var/task/node_modules/next/dist/server/next-server.js',
    '/var/task/___next_launcher.js',
    '/var/runtime/UserFunction.js',
    '/var/runtime/index.js'
  ]
}
RequestId: 1c5c0769-4fd8-4480-8b9a-08598598cd1f Error: Runtime exited with error: exit status 1
Runtime.ExitError

Weird enough, this only happens when deployed to Vercel, not when running on local.

I also confirmed that completely removing Sentry from the project solves the issue.

[tonimasc]

Also happening to me

[GET] /_next/data/NfIMoVz8P-4n3aklepICZ/es/products/fresa-vendor-madrid.json
12:20:06:40
k/node_modules/@sentry/node/dist/handlers.js

• /var/task/node_modules/@sentry/node/dist/index.js
• /var/task/node_modules/@sentry/nextjs/dist/index.server.js
• /var/task/.next/server/pages/_app.js
• /var/task/node_modules/next/dist/server/require.js
• /var/task/node_modules/next/dist/server/load-components.js
• /var/task/node_modules/next/dist/server/next-server.js
• /var/task/___next_launcher.js
• /var/runtime/UserFunction.js
• /var/runtime/index.js
  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:889:15)
  at Function.Module._load (internal/modules/cjs/loader.js:745:27)
  at Module.require (internal/modules/cjs/loader.js:961:19)
  at require (internal/modules/cjs/helpers.js:92:18)
  at Object. (/var/task/node_modules/@sentry/tracing/dist/index.js:3:17)
  at Module._compile (internal/modules/cjs/loader.js:1072:14)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
  at Module.load (internal/modules/cjs/loader.js:937:32)
  at Function.Module._load (internal/modules/cjs/loader.js:778:12)
  at Module.require (internal/modules/cjs/loader.js:961:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
  '/var/task/node_modules/@sentry/tracing/dist/index.js',
  '/var/task/node_modules/@sentry/node/dist/handlers.js',
  '/var/task/node_modules/@sentry/node/dist/index.js',
  '/var/task/node_modules/@sentry/nextjs/dist/index.server.js',
  '/var/task/.next/server/pages/_app.js',
  '/var/task/node_modules/next/dist/server/require.js',
  '/var/task/node_modules/next/dist/server/load-components.js',
  '/var/task/node_modules/next/dist/server/next-server.js',
  '/var/task/___next_launcher.js',
  '/var/runtime/UserFunction.js',
  '/var/runtime/index.js'
  ]
  }

[atilafassina]

Current workaround is to add
outputFileTracing: false to the root of your next.config.js

that will probably lead to larger artifact, but solves the issue.

output-file-tracing

[sanderkooger]

Same issue here, Sentry breaks functionality of Vercel serverless functions, but they do run locally

Workarround worked:
outputFileTracing: false to the root of your next.config.js

[cezarneaga]

getting this too. will this issue track a proper fix?

[dcastil]

Edit: These are related to Sentry and Next.js but not to the issue discussed here. Sorry, I got that mixed up.

Yes there are two open PRs at the moment:

• Ensure withSentry reports API (serverless) errors from Vercel #4044 which was a first attempt but probably won't get merged
• fix(nextjs): Delay error propagation until withSentry is done #4027 which will get merged some day hopefully. 😬

[DavidChouinard]

@davguij #4027 got merged yesterday, can you verify if the issue still exists with Sentry 6.5.0? (cc. @cezarneaga, @sanderkooger)

[cezarneaga]

works for me. thanks a bunch!