9.7.0 causes instability in instrumentation.ts

[samuelcole]

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?

@sentry/nextjs

SDK Version

9.7.0

Framework Version

Next 15.2.3

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

Upgrade from 9.6.1 to 9.7.0

Expected Result

The server boots on Vercel.

Actual Result

Uncaught Exception: TypeError: Cannot create proxy with a non-object as target or handler
 at <unknown> (.next/server/instrumentation.js:4:14174)
 at Server.<anonymous> (.next/server/instrumentation.js:4:14527)
 at <unknown> (.next/server/instrumentation.js:18:49180)
 at <unknown> (.next/server/instrumentation.js:20:108840)
 at t.with (.next/server/instrumentation.js:4:125593)
 at t.with (.next/server/instrumentation.js:20:110530)
 at e.with (.next/server/instrumentation.js:20:144801)
 at Object.withSetIsolationScope (.next/server/instrumentation.js:20:108819)
 at t.withIsolationScope (.next/server/instrumentation.js:23:7570)
Node.js process exited with exit status: 129. The logs above can help with debugging the issue.

[samuelcole]

instrumentation.ts:

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

export const register = async () => {
 if (process.env.NEXT_RUNTIME === "nodejs") {
 await import("./sentry.server.config");
 }

 if (process.env.NEXT_RUNTIME === "edge") {
 await import("./sentry.edge.config");
 }
};

export const onRequestError = Sentry.captureRequestError;

sentry.server.config.ts:

import * as Sentry from "@sentry/nextjs";
import { nodeProfilingIntegration } from "@sentry/profiling-node";

Sentry.init({
 dsn: "REDACTED",
 integrations: [Sentry.prismaIntegration(), nodeProfilingIntegration()],
 tracesSampleRate: 1,
 maxValueLength: 1000,
});

[samuelcole]

upgrade was:

- "@sentry/nextjs": "^9.6.1",
- "@sentry/profiling-node": "^9.6.1",
+ "@sentry/nextjs": "^9.7.0",
+ "@sentry/profiling-node": "^9.7.0",

[kylekz]

Also seeing this on sentry 9.3.0 & next 15.2.0 so I'm not entirely sure it's a 9.7.0 problem. This deploy (Vercel via GH actions) was made 24 hours ago and was fine, then a prod deploy 4 hours ago started showing the problem.

Updated to sentry 9.7.0 & next 15.2.3 just now, still seeing it.

Uncaught Exception: TypeError: Cannot create proxy with a non-object as target or handler
 at <unknown> (.next/server/instrumentation.js:8:64470)
 at Server.<anonymous> (.next/server/instrumentation.js:8:64823)
 at <unknown> (.next/server/instrumentation.js:25:26944)
 at <unknown> (.next/server/instrumentation.js:25:66372)
 at t.with (.next/server/instrumentation.js:12:19276)
 at t.with (.next/server/instrumentation.js:25:68062)
 at e.with (.next/server/instrumentation.js:8:48524)
 at Object.withSetIsolationScope (.next/server/instrumentation.js:25:66351)
 at t.withIsolationScope (.next/server/instrumentation.js:1:12028)
Node.js process exited with exit status: 129. The logs above can help with debugging the issue.

// instrumentation.ts
import * as Sentry from "@sentry/nextjs";
import { env } from "@repo/env";

export async function register() {
 if (env.NEXT_PUBLIC_VERCEL_ENV !== "production") {
 return;
 }

 if (process.env.NEXT_RUNTIME === "nodejs") {
 await import("../sentry.server.config");
 }

 if (process.env.NEXT_RUNTIME === "edge") {
 await import("../sentry.edge.config");
 }
}

export const onRequestError = Sentry.captureRequestError;

// sentry.server.config.ts
import { env } from "@repo/env";
import * as Sentry from "@sentry/nextjs";

Sentry.init({
 enabled: env.NEXT_PUBLIC_VERCEL_ENV === "production",
 dsn: env.NEXT_PUBLIC_SENTRY_DSN,
 tracesSampleRate: 1,
 debug: false,
});

// next.config.ts
export default withSentryConfig(withNextIntl(config), {
 org: env.SENTRY_ORG,
 project: env.SENTRY_PROJECT,
 silent: !process.env.CI,
 widenClientFileUpload: true,
 tunnelRoute: "/monitoring",
 disableLogger: true,
 automaticVercelMonitors: true,
 reactComponentAnnotation: {
 enabled: true,
 },
});

[andreiborza]

Hi @samuelcole, thanks for reporting this.

I tried to reproduce this in a fresh example project with the prisma integration and profiling-node but did not run into this. Could you please provide a reproduction repo?

Here's mine: https://github.com/andreiborza/15759-nextjs

[erikuit]

Had the same issue with Nuxt 3.16 on Vercel, but 9.8.0 fixes the issue for me.