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

davguij · 2021-10-29T07:34:07Z

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

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.

The text was updated successfully, but these errors were encountered:

tonimasc · 2021-10-29T10:23:50Z

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 · 2021-10-29T14:49:19Z

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 · 2021-11-05T18:17:35Z

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 · 2021-11-08T11:15:22Z

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

dcastil · 2021-11-08T14:36:41Z

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. 😬~~

…ing server functions @see getsentry/sentry-javascript#4103

DavidChouinard · 2021-11-16T20:16:21Z

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

cezarneaga · 2021-11-16T21:40:17Z

works for me. thanks a bunch!

bnjmnt4n · 2021-11-17T05:04:23Z

I just upgraded to @sentry/[email protected] and [email protected]. This issue still occurs:

ERROR	Error: Cannot find module '/var/task/node_modules/next/dist/server/next.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:321:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:534:18)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:888:27)
    at Function.Module._load (internal/modules/cjs/loader.js:746:27)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:93:18)
    at Object.<anonymous> (/var/task/node_modules/@sentry/nextjs/dist/utils/instrumentServer.js:8:14)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32) {  code: 'MODULE_NOT_FOUND',  path: '/var/task/node_modules/next/package.json',  requestPath: 'next'}

I believe #4027 is a separate issue to this. A comment from the Next.js maintainer seems to indicate that this issue is caused by Sentry importing a reference to next, which is disallowed on Vercel since it would increase the bundle size. ~~I'm not sure why it can't be tree-shaked~~ (Seems like there isn't any additional bundling done, and the full module is imported). Since the instrumentServer function directly modifies internals in the Next.js server, it might be good to communicate directly with the Next.js team to figure out a solution, since this seems to be a major blocker to Sentry + Next.js adoption on Vercel.

The workaround of outputFileTracing is also not a feasible long-term solution, since it severely increases the bundle size of all Next.js pages (~1.6x in my case).

davguij · 2021-11-17T08:29:13Z

@DavidChouinard I tried upgrading to @sentry/[email protected] before upgrading Next, so that it's still at [email protected] but unfortunately the original error was still there.

Then I tried upgrading Next to 12.0.4 and the original error was gone, but I'm seeing the same issue as @bnjmnt4n posted.

felixmeziere · 2021-11-17T16:23:19Z

Still have the error with 6.15.0 :/

Ryuurock · 2021-11-18T02:11:56Z

+1

IHIutch · 2021-11-18T02:26:14Z

Upgrading to 6.5.0 and setting outputFileTracing: false has worked for me

sanderkooger · 2021-11-20T13:44:08Z

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

Sure looks like it. We are starting to think to step off of sentry for a moment, until things are a bit more stable.

Disabling outputFileTracing does work. But we were looking through the history here and sentry seems to break prod quite often?

IGUNUBLUE · 2021-11-24T16:17:57Z

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

const { withSentryConfig } = require('@sentry/nextjs')

const moduleExports = {
  outputFileTracing: false
}

const sentryWebpackPluginOptions = {
  silent: true, 
}
module.exports = withSentryConfig(moduleExports, sentryWebpackPluginOptions)

Excuse me, could you please help me by indicating if this is the correct way?

dcastil · 2021-11-24T16:29:05Z

@IGUNUBLUE Yep, at least that is my current workaround.

fungilation · 2021-12-01T16:23:14Z

outputFileTracing: false does not work for me. And my crash condition is somewhat different, it crashes on SSR pages only.

What's odd to me is next build ; next start works on the same SSR pages that crash when only deployed on Vercel previews. Local dev build also works fine.

Would love to have @sentry/nextjs compatible with Next 12, as this is a pretty major blocker for Next + Sentry.

gpichot · 2022-05-12T14:15:34Z

Just adding a quick message as I stumbled on this error with using nx, sentry and next. I read too quickly the documentation and missed this part :

Make sure to add the Sentry config last; otherwise, the source maps the plugin receives may not be final.

If withSentryConfig is not the last function to applied, nextJS bundling will not work (Cannot find module '@sentry/nextjs'):

module.exports = withSentryConfig(withNx(baseOptions), {
  silent: true,
});

bigsee · 2022-10-10T15:56:40Z

Upgrading to 6.19.7 worked for me. I did not need to add outputFileTracing: false to my config.

getsantry bot added the Status: Untriaged label Oct 29, 2021

crubier mentioned this issue Oct 29, 2021

Enhancement/next 12 labelflow/labelflow#546

Merged

smeubank added the Package: nextjs Issues related to the Sentry Nextjs SDK label Nov 3, 2021

getsantry bot removed the Status: Untriaged label Nov 3, 2021

dcastil mentioned this issue Nov 5, 2021

Server functions not working on Vercel on V. 12 vercel/next.js#30601

Closed

adrianthedev mentioned this issue Nov 9, 2021

chore: try next 12 basetool-io/basetool#213

Closed

12 tasks

bamdadfr pushed a commit to bamdadfr/screwmycode-in--www that referenced this issue Nov 11, 2021

fix: disable output file tracing to prevent sentry package from crash…

a054bf5

…ing server functions @see getsentry/sentry-javascript#4103

neverether mentioned this issue Nov 16, 2021

Error to render page on NextJs 12 with fallback = true #4090

Closed

4 tasks

smeubank added this to the Next.js 12 Support milestone Nov 29, 2021

iker-barriocanal mentioned this issue Dec 1, 2021

Next.js v12 server side crashing on Vercel #4207

Closed

declanramsay mentioned this issue Dec 2, 2021

Next 12 + Sentry iqasport/iqasport.org#190

Closed

iker-barriocanal mentioned this issue Dec 10, 2021

fix(nextjs): Disable server instrumentation on Vercel #4255

Merged

iker-barriocanal linked a pull request Dec 10, 2021 that will close this issue

fix(nextjs): Disable server instrumentation on Vercel #4255

Merged

iker-barriocanal closed this as completed in #4255 Dec 10, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

davguij commented Oct 29, 2021 •

edited

Loading

tonimasc commented Oct 29, 2021

atilafassina commented Oct 29, 2021 •

edited

Loading

sanderkooger commented Nov 5, 2021 •

edited

Loading

cezarneaga commented Nov 8, 2021

dcastil commented Nov 8, 2021 •

edited

Loading

DavidChouinard commented Nov 16, 2021

cezarneaga commented Nov 16, 2021

bnjmnt4n commented Nov 17, 2021 •

edited

Loading

davguij commented Nov 17, 2021

felixmeziere commented Nov 17, 2021

Ryuurock commented Nov 18, 2021

IHIutch commented Nov 18, 2021

sanderkooger commented Nov 20, 2021

IGUNUBLUE commented Nov 24, 2021

dcastil commented Nov 24, 2021

fungilation commented Dec 1, 2021

gpichot commented May 12, 2022 •

edited

Loading

bigsee commented Oct 10, 2022

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

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

Comments

davguij commented Oct 29, 2021 • edited Loading

Package + Version

Version:

Description

tonimasc commented Oct 29, 2021

atilafassina commented Oct 29, 2021 • edited Loading

sanderkooger commented Nov 5, 2021 • edited Loading

cezarneaga commented Nov 8, 2021

dcastil commented Nov 8, 2021 • edited Loading

DavidChouinard commented Nov 16, 2021

cezarneaga commented Nov 16, 2021

bnjmnt4n commented Nov 17, 2021 • edited Loading

davguij commented Nov 17, 2021

felixmeziere commented Nov 17, 2021

Ryuurock commented Nov 18, 2021

IHIutch commented Nov 18, 2021

sanderkooger commented Nov 20, 2021

IGUNUBLUE commented Nov 24, 2021

dcastil commented Nov 24, 2021

fungilation commented Dec 1, 2021

gpichot commented May 12, 2022 • edited Loading

bigsee commented Oct 10, 2022

davguij commented Oct 29, 2021 •

edited

Loading

atilafassina commented Oct 29, 2021 •

edited

Loading

sanderkooger commented Nov 5, 2021 •

edited

Loading

dcastil commented Nov 8, 2021 •

edited

Loading

bnjmnt4n commented Nov 17, 2021 •

edited

Loading

gpichot commented May 12, 2022 •

edited

Loading