Skip to content

fix: APIPromise workaround in bundlers#1623

Merged
Stephen Belanger (Qard) merged 2 commits intomainfrom
bundled-api-promise-fix
Mar 20, 2026
Merged

fix: APIPromise workaround in bundlers#1623
Stephen Belanger (Qard) merged 2 commits intomainfrom
bundled-api-promise-fix

Conversation

@Qard
Copy link
Contributor

No description provided.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we add a regression test somehow?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wow anthropic is so annoying with this non standard behaviour. I don't even understand why they need to do it either.

@AbhiPrasad Abhijeet Prasad (AbhiPrasad) changed the title Fix APIPromise workaround in bundlers fix: APIPromise workaround in bundlers Mar 20, 2026
@Qard Stephen Belanger (Qard) force-pushed the bundled-api-promise-fix branch 3 times, most recently from 5fc9174 to 1c48542 Compare March 20, 2026 16:30
Auto-instrumented spans now produce context:{} instead of
context:{caller_filename:"<node-internal>",...} because patchTracingChannel
is bundled into index.mjs alongside getCallerLocation. When all stack
frames share the same directory, getCallerLocation returns undefined.

The <node-internal> value was an artifact of the native C++ tracePromise
call stack, not meaningful user code location info.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Qard Stephen Belanger (Qard) merged commit 201d504 into main Mar 20, 2026
49 checks passed
@Qard Stephen Belanger (Qard) deleted the bundled-api-promise-fix branch March 20, 2026 19:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants