sentry-javascript: Crash on server side running on Vercel after upgrading to Next.js 12

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

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.

I just upgraded to @sentry/nextjs@6.15.0 and next@12.0.4. 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).

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

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

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:

• https://github.com/getsentry/sentry-javascript/pull/4044 which was a first attempt but probably won’t get merged
• https://github.com/getsentry/sentry-javascript/pull/4027 which will get merged some day hopefully. 😬

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,
});

+1

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