Uh oh!
There was an error while loading. Please reload this page.
feat(node): move dc integration swap to _init - #22173
Conversation
size-limit report 📦
|
7b12bae to
63a580fCompare63a580f to
89c3b4cCompare89c3b4c to
1d877dfCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
1d877df to
5d4d988CompareThere was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 5d4d988. Configure here.
Uh oh!
There was an error while loading. Please reload this page.
5d4d988 to
b2a369dCompareMove the diagnostics-channel integration swap out of `getDefaultIntegrations` and into `_init`, so it also applies to framework SDKs that pass their own `defaultIntegrations` array, and is skipped when defaults are explicitly empty. This will be needed because the NestJS SDK (and others) build on top of the Node SDK, but swap out their default integrations.
b2a369d to
56289c4Compare
JPeer264
left a comment
There was a problem hiding this comment.
LGTM.
super-l: I think this is more of a fix than a feat, but that's a nit and can be ignored.
isaacs
commented
Jul 13, 2026
Oh, no, that's actually a great point. Idk what I was thinking, users 100% do not need this in the changelog 😅 I'll edit the commit headline and merge. |

Move the diagnostics-channel integration swap out of
getDefaultIntegrationsand into_init, so it also applies to framework SDKs that pass their owndefaultIntegrationsarray, and is skipped when defaults are explicitly empty.This will be needed because the NestJS SDK (and others) build on top of the Node SDK, but swap out their default integrations.