[Bug]: Inconsistent hybrid module resolution (index.d.mts vs. index.d.cts) between ts-jest and tsc about ts-jest

[vekexasia]

out of curioisty how do you force to esnext?

[chriswheeldon-peakon]

@vekexasia

diff --git a/src/legacy/compiler/ts-compiler.ts b/src/legacy/compiler/ts-compiler.ts
index 5ef5f3df8..1b65722b0 100644
--- a/src/legacy/compiler/ts-compiler.ts
+++ b/src/legacy/compiler/ts-compiler.ts
@@ -402,6 +402,8 @@ export class TsCompiler implements TsCompilerInstance {
       this._moduleResolutionHost!,
       // eslint-disable-next-line @typescript-eslint/no-non-null-assertion
       this._moduleResolutionCache!,
+      undefined,
+      this._ts.ModuleKind.ESNext,
     )
   }

[chriswheeldon-peakon]

I managed to work around this (without modifying the ts-jest source) by using a local declaration file that forces resolution to the d.mts export from helmet:

/// <reference path="./node_modules/helmet/index.d.mts" />

declare module "helmet" {
  export default helmet;
  export * from "helmet";
}

I've applied to the same kind of workaround successfully to two other hybrid modules that confuse ts-jest.