I have a build step which transpiles my TypeScript code to regular JavaScript with source maps. When using console.error or anything else that shows a stack trace, I expect bun to show me the stack trace from my source.
What is the feature you are proposing to solve the problem?
Either support existing source maps by default or put it behind a flag, like Node.js's --enable-source-maps flag.
What alternatives have you considered?
I'm aware that bun can transpile files which workarounds this issue. But it would be great to have support regardless.
What is the problem this feature would solve?
I have a build step which transpiles my TypeScript code to regular JavaScript with source maps. When using
console.error
or anything else that shows a stack trace, I expect bun to show me the stack trace from my source.What is the feature you are proposing to solve the problem?
Either support existing source maps by default or put it behind a flag, like Node.js's
--enable-source-maps
flag.What alternatives have you considered?
I'm aware that bun can transpile files which workarounds this issue. But it would be great to have support regardless.