All first lines uncovered when using c8 with tsx --test

[rozzilla]

Acknowledgements

• I read the documentation and searched existing issues to avoid duplicates
• I am reporting a confirmed bug (not seek debugging help)
• I understand this is a collaborative project and relies on my contributions
• I read and understood the Contribution guide

Minimal reproduction URL

https://github.com/rozzilla/c8-tsx-coverage-issue

Problem & expected behavior (under 200 words)

As you can see from the repro, even though I have a test covering the whole file, the coverage result return the 1st line as uncovered

Bugs are expected to be fixed by those affected by it

• I'm interested in working on this issue

Compensating engineering work financially will speed up resolution

• I'm willing to offer financial support

[privatenumber]

tsx is just using the Node APIs so I'm not sure if this is a bug in tsx or if there's even anything we can do on our end.

This may be related:
nodejs/node#53315

[rozzilla]

To better explain the issue, this doesn't happen with `nyc` Il Gio 6 Giu 2024, 08:49 Hiroki Osame ***@***.***> ha scritto:

…

tsx is just using the Node APIs so I'm not sure if this is a bug in tsx or if there's even anything we can do on our end. This may be fixed by: nodejs/node#53315 <nodejs/node#53315> — Reply to this email directly, view it on GitHub <#564 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6PVA775WISR2WJHCGOYP3ZGAA7VAVCNFSM6AAAAABIQOEAMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJRGUZTCOBSGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[privatenumber]

Not sure if I understand how that better explains the issue...

If you want to get to the bottom of this, I recommend inlining the sourcemap as a minimal reproduction and filing an issue with Node.

[privatenumber]

Locking as this seems blocked by Node. Feel free to open an issue there if it doesn't exist yet.