Type definition and runtime for tsconfig option does not agree

[jimisaacs]

🐛 Bug Report

When specifying inline compiler options, in typescript, it say it must be of the type _ts.CompilerOptions, though this is incorrect. As ts-jest expects the JSON format shape, not the API format shape.

An example is the jsx option, which takes a value of type JsxEmit, which is an enum that looks like this:

export enum JsxEmit {
    None = 0,
    Preserve = 1,
    React = 2,
    ReactNative = 3,
    ReactJSX = 4,
    ReactJSXDev = 5
}

Though ts-jest expects strings 'react' | 'preserve' | ... etc. which it actually complains and tells you about at runtime.

To Reproduce

Steps to reproduce the behavior:

Create a jest.config.ts file and attempt to create a config object of type InitialOptionsTsJest. Then try to provide inline options such as config.globals.tsconfig.jsx = 'react';

Expected behavior

My expectation is to use the file format, because it would allow for overrides like this:

import tsconfig from './tsconfig.json';

const config = {
    globals: {
        'ts-jest': {
            tsconfig: {
                ...tsconfig.compilerOptions,
                jsx: 'react',
            },
        },
    },
};

I think this is the intent for ts-jest, but the types are just wrong IMO.

Link to repo (highly encouraged)

Debug log:

# content of ts-jest.log :

envinfo

System:
    OS:
    Node version:

Npm packages:
    jest:
    ts-jest:
    typescript:
    babel(optional):