Sourcemap is ignored if file contains dynamic import

[BenceSzalai]

Problem

Dependency files that:

• include ESM dynamic imports
• has sourcemaps associated (generated by TSC)

show up in Error stack traces:

• with .js extension (as opposed to .ts)
• with wrong line numbers
• and with their real file path instead of the original path based on the sourcemap

i.e. their source maps are ignored.

Expected behavior

All dependency files that has sourcemaps associated should show up in Error stack traces with their original path, extension and line numbers.

Minimal reproduction URL

https://github.com/BenceSzalai/tsx-sm-issue

Version

v3.12.7

Node.js version

v18.17.0 / v20.5.1

Package manager

npm

Operating system

macOS

Contributions

• I plan to open a pull request for this issue
• I plan to make a financial contribution to this project

[BenceSzalai]

Note, I've just updated the reproduction repo to compare with the equivalent non-TSX Node.js behaviour which uses sourcemaps correctly, so surprisingly it is only happening with TSX.

[BenceSzalai]

On the other hand I've just compared the behaviour with the ESM Loader usage, and it looks like it is caused by ESM Loader, so I'll raise it there instead.