use ts-node field from extended tsconfig

[stefanprobst]

Desired Behavior

currently it is possible to define a ts-node field in tsconfig.json for configuration, but when extending from a tsconfig package, which has a ts-node field, that config is not used.

For example, in my project i have:

{
  "extends": "@stefanprobst/tsconfig"
}

and that npm package provides a tsconfig.json which has:

{
  "ts-node": {
    "compilerOptions": {
      "module": "commonjs"
    }
  }
}

Is this request related to a problem?

it would allow me to define a "ts-node" config field once in a tsconfig npm package, and extend it in my projects

Alternatives you've considered

put ts-node config field directly in project's tsconfig.json.

Additional context

[cspotcode]

This is a dupe and has already been implemented.

…

On Thu, Jul 1, 2021, 9:25 AM stefanprobst ***@***.***> wrote: Desired Behavior currently it is possible to define a ts-node field in tsconfig.json for configuration, but when extending from a tsconfig package, which has a ts-node field, that config is not used. For example, in my project i have: { "extends": ***@***.***/tsconfig" } and that npm package provides a tsconfig.json which has: { "ts-node": { "compilerOptions": { "module": "commonjs" } } } Is this request related to a problem? it would allow me to define a "ts-node" config field once in a tsconfig npm package, and extend it in my projects Alternatives you've considered put ts-node config field directly in project's tsconfig.json. Additional context — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1382>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC35OBW523F7ZU67PQZ72DTVRUFFANCNFSM47UXBSBA> .

[stefanprobst]

thanks!

for reference: #1356 (not released yet)