startTransaction() returns undefined contrary to what its return type claims

[wereHamster]

startTransaction() returns undefined contrary to what its return type claims

[wereHamster]

The Sentry.startSpan() API seems to be more honest about what it does, the callback argument is explicitly marked as nullable.

[wereHamster]

Wait, what? Importing @sentry/tracing makes it work?!?

import * as Sentry from "@sentry/node"
import "@sentry/tracing"

const transaction = Sentry.startTransaction({
  name: `test`,
})
console.log('tx', transaction)

Still, a function claiming to never return undefined returning undefined is… unexpected.

[lforst]

Generally speaking, I agree, this is stupid. We made a trade-off for tree-shaking.

You must be on a pretty old SDK version though, as when using startTransaction() after init() from @sentry/node should should always return a transaction.

[wereHamster]

I tested with 7.94.1, which is the latest version as of now.

https://codesandbox.io/p/devbox/affectionate-breeze-r93zts

[lforst]

@wereHamster You would need to add a call to init(). However, I should add startTransaction and startChild are deprecated and are soon gonna be removed. They are replaced by Sentry.startSpan() which has correct typing.

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀