No coverage when using self-references

[RebeccaStevens]

• Version: v18.15.0
• Platform: Linux Beka-PC 5.10.102.1-microsoft-standard-WSL2 Detailed coverage #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

I'm trying to use self-referencing in my test files, but when I do so, I no longer get the correct coverage results.
(A relative import gets the right results).

import foo from "../src/index.ts"; // Finds coverage.
import foo from "my-package";      // Doesn't finds coverage.

My tsconfig.json file contains the dev mapping:

{
  "rootDir": ".",
  "paths": {
    "my-package": ["./src/index.ts"],
  }
}

And my package.json contains the dist mappings:

{
  "name": "my-package",
  "exports": {
    "types": {
      "import": "./dist/index.d.mts",
      "require": "./dist/index.d.cts"
    },
    "import": "./dist/index.mjs",
    "require": "./dist/index.cjs"
  }
}

I'm using ava to run the tests, here's its config (ava.config.mjs):

const avaConfig = {
  files: ["tests/**/*.test.*"],
  timeout: "5m",
  extensions: {
    ts: "module",
  },
  require: [
    "tsconfig-paths/register"
  ],
  nodeArguments: [
    "--loader=ts-node/esm",
    "--experimental-specifier-resolution=node",
  ],
};

export default avaConfig;

[RebeccaStevens]

Looks like this issue might be that the dist files are being loaded, not the src files.
I'll need to do some more testing; I'll close if this is indeed the cause.

[RebeccaStevens]

Looks like it was that issue. Using --loader=ts-paths-esm-loader fixed the issue.