Performance is not defined - sentry with NextJS

[jlkravitz]

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

10.2.0

Framework Version

14.0.4

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

1. Ran npx @sentry/wizard@latest -i nextjs --saas --org <ORG> --project <PROJECT>
2. Ran npm run dev
3. Opened browser

Expected Result

No error.

Actual Result

I keep getting a performance is not defined error

[linear]

JS-840 Performance is not defined - sentry with NextJS

[Lms24]

Hey @jlkravitz thanks for writing in! Are you using any Opentelemetry packages or something like @vercel/otel?

Looks like browser code is imported into the edge build on first glance.

[jlkravitz]

Hey @Lms24 ! We're not on vercel at all. That said, I tried upgrading to Next 15.x and everything seems OK now? Happy to provide additional details if you'd like to try to debug, but I should be OK for now, despite the continued mystery...

[Lms24]

hmm, NextJS 14 should still be supported by our SDK in v10. So if there's a bug we should fix it. I'll try to repro this myself for now, just to be sure this doesn't happen on every project. In case I can't reproduce, we either need a reproduction from you, or, if you're happy with the current state on Next 15, I'd rather close this for now (and reopen if anyone else comes across this issue).

We're not on vercel at all

Can you tell me more about your build and deployment setup? Are you doing anything special when building?
UPDTAE: I realized you reported this happening in dev mode already, so likely it's not related to your build.