sentry-javascript: Next.js Class extends value undefined is not a constructor or null on v7.89.0
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
SDK Version
7.89.0
Framework Version
7.89.0
Link to Sentry event
SDK Setup
if (process.env.NODE_ENV === 'production') {
nextConfig = withSentryConfig(
nextConfig,
{
// For all available options, see:
// https://github.com/getsentry/sentry-webpack-plugin#options
// Suppresses source map uploading logs during build
silent: true,
org: 'my-org',
project: 'my-app-nextjs',
},
{
// For all available options, see:
// https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/
// Upload a larger set of source maps for prettier stack traces (increases build time)
widenClientFileUpload: true,
// Transpiles SDK to be compatible with IE11 (increases bundle size)
transpileClientSDK: false,
// Routes browser requests to Sentry through a Next.js rewrite to circumvent ad-blockers (increases server load)
tunnelRoute: '/monitoring',
// Hides source maps from generated client bundles
hideSourceMaps: true,
// Automatically tree-shake Sentry logger statements to reduce bundle size
disableLogger: true,
// Enables automatic instrumentation of Vercel Cron Monitors.
// See the following for more information:
// https://docs.sentry.io/product/crons/
// https://vercel.com/docs/cron-jobs
automaticVercelMonitors: false,
}
);
}
Steps to Reproduce
In my Next v14.1.0 app, I loaded a page, when a component seems to change inside the page, it caused an error from Sentry:
Class extends value undefined is not a constructor or null
This might be caused by a React Class Component being rendered in a Server Component, React Class Components only works in Client Components. Read more: https://nextjs.org/docs/messages/class-component-in-server-component
I have worked out the code that is the problem is within a server-only function which is loaded on every page to fetch user data from my API, this function is also where I am setting the user for Sentry.
import 'server-only';
import { cache } from 'react';
import { cookies } from 'next/headers';
import * as Sentry from '@sentry/nextjs';
/**
* Fetch user's data
* @returns {User | null}
*/
export const fetchUser = cache(async (): Promise<User | null> => {
const res = await fetch(`${API_ENDPOINT}/keyusers/?current=True`, {
headers: {
Cookie: `sessionid=${cookies().get('sessionid')?.value}`,
'Content-Type': 'application/json',
},
});
if (!res.ok) {
return null;
}
const data = await res.json();
Sentry.setUser({ id: data.results[0].id });
return data.results[0];
});
If I comment the Sentry parts out, everything works as expected.
This error doesn’t occur on v7.88.0 of @sentry/nextjs, so am stuck on this version for now. I use this function in several places within my monorepo, so am unable to upgrade Sentry until I can find a solution here.
Expected Result
No errors in the console to occur
Actual Result
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Reactions: 6
- Comments: 20 (9 by maintainers)
Commits related to this issue
- Fixed errors triggered by server actions due to latest updates https://github.com/getsentry/sentry-javascript/issues/10366 — committed to FlorianLeChat/Simple-File-Storage by FlorianLeChat 4 months ago
- fix(nextjs/v7): Use passthrough `createReduxEnhancer` on server (#11010) Fixes https://github.com/getsentry/sentry-javascript/issues/10366 — committed to getsentry/sentry-javascript by lforst 4 months ago
Probably related to https://github.com/vercel/next.js/pull/61194, I was able to fix this issue in dev mode by adding manually in next config:
Note by SDK author (@lforst): The above was a workaround for this issue that now has been fixed with version
7.106.1of the Sentry Next.js SDK. The workaround is harmful to your cold-start times and we highly recommend removing it after upgrading!Don’t mind me, Just want to shout out @meienberger for saving my day because this error is so cryptic, I’d spend hours, if not days debugging it.
@nbolton right. Thanks for the heads up!
@meienberger Thanks again for providing the workaround. I edited your comment to point people towards upgrading the SDK. I hope that’s ok!
@avarayr Thank you very much for confirming!
I highly recommend not putting
@sentry/nextjsand@sentry/nodein the external packages config. It has a non-trivial effect on cold-starts and may break certain SDK features in the future. We actually made an effort in collaboration with Vercel to remove the SDK from being external by default in Next.js: https://github.com/vercel/next.js/pull/61194It is really important for us moving forward because this was necessary for us to have directives like
"use client"in the SDK.I can confirm this workaround fixed it. I almost stopped reading at this point but decided to check the latest comments and saw that the correct fix is actually:
@lforst Thanks to the Sentry team for fixing this.
Hi everybody, we just released version
7.106.1of the SDK which should address this issue. Please try it out and feel free to let us know if the fix worked (or not). Cheers!I’m experiencing this error as well. It happens in Next.js 14, only in dev mode, when some server action is triggered.
I’m on next js 14.1 and I have the same error when I perform a server action. It does seem to me Next using the cjs version of @sentry/react is the cause of the error as I find the following in the log