Repository navigation
Performance is not defined - sentry with NextJS #17343
Description
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
- Ran
npx @sentry/wizard@latest -i nextjs --saas --org <ORG> --project <PROJECT> - Ran
npm run dev - Opened browser
Expected Result
No error.
Actual Result
I keep getting a performance is not defined error
Metadata
Metadata
Assignees
Projects
- Status
Activity
linear commentedon Aug 6, 2025
JS-840 Performance is not defined - sentry with NextJS
Lms24 commentedon Aug 6, 2025
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 commentedon Aug 6, 2025
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 commentedon Aug 7, 2025
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).
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.
12 remaining items
andreiborza commentedon Aug 14, 2025
Thanks, that'll help us narrow it down better.
khanprog commentedon Aug 26, 2025
Is there any update on this issue?
andreiborza commentedon Aug 26, 2025
Hi, we're still looking into it. cc @chargome
chargome commentedon Aug 26, 2025
Did someone try nuking
node_modulesand go with a fresh install already?andreiborza commentedon Aug 26, 2025
Thanks again for the reproduction, can confirm it happens when adding middleware. Look like the edge instrumentation somehow ends up with browser-related imports. Need to dig deeper.
fix(nextjs): Add edge polyfills for nextjs-13 in dev mode (#17488)
github-actions commentedon Sep 16, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #17488, which was included in the 10.12.0 release.