Skip to content

use ts-node field from extended tsconfig #1382

Description

@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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions