Coverage with c8 and tsx reporting as 100% since version 4.3.0

[OscarBarrett]

Acknowledgements

• I searched existing issues before opening this one to avoid duplicates
• I understand this is not a place for seek help, but to report a bug
• I understand that the bug must be proven first with a minimal reproduction
• I will be polite, respectful, and considerate of people's time and effort

Minimal reproduction URL

https://github.com/OscarBarrett/tsx-coverage-issue

Version

v4.6.2

Node.js version

v20.10.0

Package manager

yarn

Operating system

Linux

Problem & Expected behavior

We use c8 and tsx together when running our test suites, and since tsx version 4.3.0 any file that is imported in our tests gets 100% coverage.
Locking to tsx 4.2.1, we get the expected coverage.

Assuming this is related to #405

Contributions

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

[andreashuber69]

I have the same issue. FWIW, you can work around this by running tests on the built js output. If you have TypeScript generate .map files, then the CC output should look the same as before (i.e. reported on ts files rather than js files). Here's an example of the changes necessary (besides building with tsc):

andreashuber69/verify-coldcard-dice-seed@35b72b9

[privatenumber]

I haven't investigated this but I'm thinking this is as simple as removing this check so sourcemaps are always inlined:

tsx/src/source-map.ts

Line 23 in 8c77891

if (hasNativeSourceMapSupport) {

There will need to be tests though. PR welcome if anyone wants to tackle.

[privatenumber]

Sorry, I'm going to hide your comment because it doesn't lead to a solution in tsx.

Seems like both versions of tsx in the reproduction doesn't work in the latest version of Node, but the reproduction still works fine with Node v20.10.0.

I'm curious what happened between tsx v4.2.1 and v4.6.2 that broke c8 in Node v20.10.0.

[cenfun]

@privatenumber the generated sourcemap content could be different
could be caused by this

/**
	 * Improve performance by generating smaller source maps
	 * that doesn't include the original source code
	 *
	 * https://esbuild.github.io/api/#sources-content
	 */
	sourcesContent: false,

[privatenumber]

@cenfun

You're right!

I tested removing sourcesContent (https://github.com/privatenumber/tsx/compare/esbuild-sourcesContent?expand=1) in the reproduction and the coverage is working again in Node 20.10.0 and v20.12.1 (latest LTS):

pnpm i 'privatenumber/tsx#npm/esbuild-sourcesContent'

(Here's how to make a installable branch, if you're interested)

I'll need to look into a way to add tests for this.

[privatenumber]

This has been completed in the development repo.

[privatenumber]

🎉 This issue has been resolved in v4.10.4

If you appreciate this project, please consider supporting this project by sponsoring ❤️ 🙏

[wellwelwel]

🎉 This issue has been resolved in v4.10.4

An observation that I find interesting to relate is that after v4.10.4, the coverage of a project dropped by almost 2%.
Looking at the differences between tsx versions, I noticed that it was mainly the imports of types.

To fix it, I just used c8's recommendation:

/* c8 ignore next */
import type { SomeType } from '../some-type.js';

• I don't see this as an issue, so I preferred to add it to the context of this issue.

@privatenumber, thanks for this project and the fix 💙

[rozzilla]

Hi @privatenumber 👋🏼 😊
I also have a similar issue. I opened it here.