Bug: Error stack trace file paths don't use source maps

[kristianeboe]

Describe the bug
Both console log and loglevel, and debug, manage to parse source maps (I think that's the issue?) to create a clear stack trace with hyper links, but tslog does not :(

To Reproduce
Steps to reproduce the behavior:

1. Log an error

Expected behavior
produce the same trace as console log and other tools

Additional context
I'm on bun and nextjs 14

Node.js Version
20

[kylecordes]

This is disappointing. I had hoped that a logging tool with TS in the name would "just work" with TypeScript - showing stack traces based on source maps.

[marijnbent]

Same for me

[terehov]

Still open. v5 rewrote and unified stack parsing, but it still reports the transpiled file position — it does not consume source maps to map frames back to original .ts sources. Tools like console.log/debug get clickable original locations because the runtime/devtools apply the source map, not the logger. Source-map-aware trace resolution would be a new feature; keeping this open as an enhancement request rather than closing it against v5.