Put TypeScript configuration in react-scripts instead of individual project? (TS3.2+)

Is this a bug report?

No

Motivation

TypeScript 3.2, released November 29th, 2018, now uses Node.js-based resolution for tsconfig.json inheritance

TypeScript 3.2 now resolves tsconfig.jsons from node_modules. When using a bare path for the "extends" field in tsconfig.json, TypeScript will dive into node_modules packages for us.

{
    "extends": "@my-team/tsconfig-base",
    "include": ["./**/*"]
    "compilerOptions": {
        // Override certain options on a project-by-project basis.
        "strictBindCallApply": false,
    }
}

TypeScript will look for "tsconfig" field in package.json to determine the configuration file to use.

Therefore, the generated tsconfig.json could be reduced to

{ "extends": "react-scripts", "include": ["src"] }

This would further reduce configuration in create-react-app projects.

[Timer]

Yay! We requested this over a year and a half ago: https://github.com/Microsoft/TypeScript/issues/15984

[dtinth]

Hiding the configuration doesn’t make it unconfigurable.

TypeScript configs like target, lib, jsx, no*, etc can evolve over time as browser tech evolve. The goal should be to allow users to upgrade to latest practice by just upgrading react-scripts and not have to copy the latest tsconfig.json from the source code.