Skip to content

[Bug]: customConditions are not reset in fixupCompilerOptionsForModuleKind #4620

@Knagis

Description

@Knagis

Version

29.2.5

Steps to reproduce

use a tsconfig with

        "module": "preserve",
        "moduleResolution": "bundler",
        "customConditions": [
            "node",
        ],

Expected behavior

ts-jest transpiles .ts files

Actual behavior

  ● Test suite failed to run

    error TS5098: Option 'customConditions' can only be used when 'moduleResolution' is set to 'node16', 'nodenext', or 'bundler'.

Debug log

Additional context

https://github.com/kulshekhar/ts-jest/blob/main/src/legacy/compiler/ts-compiler.ts#L155 sets moduleResolution: "node" but it doesn't reset customConditions which are not supported with the new moduleResolution value. Adding customConditions: undefined works well.

Environment

System:
    OS: Windows 10 10.0.26100
    CPU: (16) x64 Intel(R) Core(TM) i7
  Binaries:
    Node: 22.11.0 - ~\AppData\Local\nvs\default\node.EXE
    Yarn: 4.1.1 - ~\AppData\Local\nvs\default\yarn.CMD
    npm: 10.9.0 - ~\AppData\Local\nvs\default\npm.CMD
  npmPackages:
    jest: 29.7.0 => 29.7.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions