ts-jest 29.4.10 → 29.4.11

package/.ts-jest-digest

@@ -1 +1 @@
-19e702f0a49983ce6d92683fb1199ea2acf8e36a
+73233cd15fa36234d30a07a1efa9643162305524

package/CHANGELOG.md

@@ -1,3 +1,12 @@
+## [29.4.11](https://github.com/kulshekhar/ts-jest/compare/v29.4.10...v29.4.11) (2026-05-21)
+
+
+### Bug Fixes
+
+* preserve Bundler on the CJS path under TypeScript >= 6 ([3941818](https://github.com/kulshekhar/ts-jest/commit/39418187515f11b6584d35a4e3ddf50231f74936)), closes [#4198](https://github.com/kulshekhar/ts-jest/issues/4198)
+
+
+
 ## [29.4.10](https://github.com/kulshekhar/ts-jest/compare/v29.4.9...v29.4.10) (2026-05-18)
 
 

package/dist/legacy/compiler/ts-compiler.d.ts

@@ -66,11 +66,11 @@ export declare class TsCompiler implements TsCompilerInstance {
      *     supports.)
      *
      *   - User-supplied Bundler with a non-Bundler-compatible forced module is
-     *     also TS5095 on the supported TS range — substitute Node10. (TypeScript
-     *     6 relaxed this for `module: CommonJS` specifically; that relaxation is
-     *     deliberately not encoded here so behavior stays consistent across the
-     *     full peerDependency range. See `isBundlerCompatibleModuleKind` for the
-     *     follow-up pointer.)
+     *     TS5095, substitute Node10. (TypeScript 6 relaxed this for
+     *     `module: CommonJS` specifically; that relaxation is encoded inside
+     *     `isBundlerCompatibleModuleKind` via a runtime version check, so on
+     *     TS ≥ 6 user-supplied Bundler passes through unchanged on the CJS
+     *     path.)
      *
      *   - Anything else (Node10 / Classic / unset) passes through or falls back
      *     to Node10. These pairings are valid with every forced module kind.
@@ -94,13 +94,12 @@ export declare class TsCompiler implements TsCompilerInstance {
      * user-supplied-`Bundler` pass-through, so neither path emits an invalid
      * pair when the user has selected a non-ES `module`.
      *
-     * Note: TypeScript 6.0 relaxed this restriction for `module: CommonJS`
-     * specifically (`CommonJS` + `Bundler` is now a valid pair on TS ≥ 6); the
-     * other non-ES module kinds (`AMD` / `UMD` / `System` / `None`) remain
-     * Bundler-incompatible on every TypeScript version. The TS 6 relaxation is
-     * intentionally not encoded here to keep behavior consistent across the full
-     * peerDependency range (`>=4.3 <7`); honoring it can ride in as a follow-up
-     * once the TS 6 baseline lands.
+     * TypeScript 6.0 relaxed TS5095 for `module: CommonJS` specifically
+     * (`CommonJS` + `Bundler` is a valid pair on TS ≥ 6); the other non-ES
+     * module kinds (`AMD` / `UMD` / `System` / `None`) remain Bundler-incompatible
+     * on every TypeScript version. The version is detected at runtime from
+     * `this._ts.version` so the function stays correct across the full
+     * peerDependency range (`>=4.3 <7`).
      *
      * @see https://www.typescriptlang.org/tsconfig/#moduleResolution
      */

package/dist/legacy/compiler/ts-compiler.js

@@ -181,11 +181,11 @@ class TsCompiler {
      *     supports.)
      *
      *   - User-supplied Bundler with a non-Bundler-compatible forced module is
-     *     also TS5095 on the supported TS range — substitute Node10. (TypeScript
-     *     6 relaxed this for `module: CommonJS` specifically; that relaxation is
-     *     deliberately not encoded here so behavior stays consistent across the
-     *     full peerDependency range. See `isBundlerCompatibleModuleKind` for the
-     *     follow-up pointer.)
+     *     TS5095, substitute Node10. (TypeScript 6 relaxed this for
+     *     `module: CommonJS` specifically; that relaxation is encoded inside
+     *     `isBundlerCompatibleModuleKind` via a runtime version check, so on
+     *     TS ≥ 6 user-supplied Bundler passes through unchanged on the CJS
+     *     path.)
      *
      *   - Anything else (Node10 / Classic / unset) passes through or falls back
      *     to Node10. These pairings are valid with every forced module kind.
@@ -224,13 +224,12 @@ class TsCompiler {
      * user-supplied-`Bundler` pass-through, so neither path emits an invalid
      * pair when the user has selected a non-ES `module`.
      *
-     * Note: TypeScript 6.0 relaxed this restriction for `module: CommonJS`
-     * specifically (`CommonJS` + `Bundler` is now a valid pair on TS ≥ 6); the
-     * other non-ES module kinds (`AMD` / `UMD` / `System` / `None`) remain
-     * Bundler-incompatible on every TypeScript version. The TS 6 relaxation is
-     * intentionally not encoded here to keep behavior consistent across the full
-     * peerDependency range (`>=4.3 <7`); honoring it can ride in as a follow-up
-     * once the TS 6 baseline lands.
+     * TypeScript 6.0 relaxed TS5095 for `module: CommonJS` specifically
+     * (`CommonJS` + `Bundler` is a valid pair on TS ≥ 6); the other non-ES
+     * module kinds (`AMD` / `UMD` / `System` / `None`) remain Bundler-incompatible
+     * on every TypeScript version. The version is detected at runtime from
+     * `this._ts.version` so the function stays correct across the full
+     * peerDependency range (`>=4.3 <7`).
      *
      * @see https://www.typescriptlang.org/tsconfig/#moduleResolution
      */
@@ -244,6 +243,11 @@ class TsCompiler {
         if (M.Preserve !== undefined && moduleKind === M.Preserve) {
             return true;
         }
+        // TS 6 made `CommonJS` + `Bundler` a valid pair.
+        if (moduleKind === M.CommonJS) {
+            const tsMajor = parseInt(this._ts.version.split('.')[0], 10);
+            return tsMajor >= 6;
+        }
         return false;
     }
     /**

package/npm-view.err

@@ -0,0 +1,9 @@
+npm warn Unknown user config "always-auth". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
+npm error code E404
+npm error 404 No match found for version 29.4.11
+npm error 404
+npm error 404  The requested resource 'ts-jest@29.4.11' could not be found or you do not have permission to access it.
+npm error 404
+npm error 404 Note that you can also install from a
+npm error 404 tarball, folder, http url, or git url.
+npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-05-21T13_47_16_595Z-debug-0.log

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ts-jest",
-  "version": "29.4.10",
+  "version": "29.4.11",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "commonjs",