fix(v10/nextjs): Register Vercel AI span processors on Next.js - #23773
Merged
Conversation
Member
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 3965bd0. Configure here.
Contributor
size-limit report 📦
|
Member
Author
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 9a83b45. Configure here.
Next.js bundles `ai`, so the module is never patched and the `Modules` detection fallback misses workspace and transitive deps, leaving the AI SDK's raw `ai.*` spans unprocessed. Register the processors in `init` after the client exists, so an explicitly constructed `vercelAIIntegration()` cannot override it, and make `addVercelAiProcessors` idempotent. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
chargome
force-pushed
the
charlygomez/tet-2891-vercel-ai-nextjs-v10
branch
from
August 31, 2026 15:54
9a83b45 to
e36dde0
Compare
chargome
marked this pull request as ready for review
September 1, 2026 06:02
chargome
requested review from
RulaKhaled,
andreiborza,
nicohrubec and
s1gr1d
and removed request for
a team
September 1, 2026 06:02
RulaKhaled
approved these changes
Sep 1, 2026
chargome
added a commit
to getsentry/sentry-docs
that referenced
this pull request
Sep 1, 2026
## DESCRIBE YOUR PR
On Next.js, `experimental_telemetry: { isEnabled: true }` is required on
every AI SDK call in **both** the Node and Edge runtimes — the page
scoped this to Edge and claimed the Node runtime patches call sites for
you.
The troubleshooting entry for raw span names presented `force: true` as
the whole fix, but alone it only registers the span processors and
yields zero AI spans; it now spells out both required steps. Verified on
`@sentry/nextjs@10.71.0`, Next.js 16.3.3, `ai@6`.
Also trimmed the Node/Edge split down to where the runtimes actually
differ. Not version-gated, since the fix that makes `force: true`
unnecessary (getsentry/sentry-javascript#23773) is unreleased. The page
is shared across ~25 platforms — every edit is inside a
`javascript.nextjs` `<PlatformSection>`.
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ai.generateText/ai.toolCall, nogen_aiopai, so it is never patched, and theModulesfallback misses workspace and transitive depsinitrather than on the default integration, which a user-suppliedvercelAIIntegration()would replaceaihidden fromModules, and this gating is gone in v11experimental_telemetry: { isEnabled: true }; docs to followRef: https://linear.app/getsentry/issue/TET-2891/vercel-ai-sdk-v6-instrumentation-is-broken-on-nextjs