Skip to content

Dump the effective config file #15213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
alexewerlof opened this issue Apr 16, 2017 · 1 comment
Closed

Dump the effective config file #15213

alexewerlof opened this issue Apr 16, 2017 · 1 comment
Labels
Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Suggestion An idea for TypeScript

Comments

@alexewerlof
Copy link

Suggestion

I'm using Typedoc which has very similar options to tsc and book keeping and converting these options is tedious and error prone. It would be nice if tsc could dump its effective compiler options (considering the default values, extends rules, etc.) as a json file. This can be particularly useful when debugging the configurations to see what config is effectively being used for the compilation process.

See: TypeStrong/typedoc#480

TypeScript Version: 2.2.1 / nightly (2.2.0-dev.201xxxxx)

Expected behavior:

tsc --effectiveConfig
# Prints out a json object on STDOUT that is ready to be redirected to a JSON file
{
    "compilerOptions": {
        "module": "commonjs",
        "sourceMap": true,
        "target": "es2016",
        "noEmitOnError": true,
        "alwaysStrict": true,
        "importHelpers": true,
        "lib": [
            "es2015"
        ]
        ...
    }
}
@RyanCavanaugh RyanCavanaugh added Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Suggestion An idea for TypeScript labels Apr 17, 2017
@huafu
Copy link

huafu commented Jul 6, 2018

I was looking for an option on how to output the effective config when I found this. I'm stuck since an hour trying to find out how extends actually extends stuff. I could only find in the docs:

files, include and exclude from the inheriting config file overwrite those from the base config file.

All relative paths found in the configuration file will be resolved relative to the configuration file they originated in.

But nothing about what happens to deeper arrays such as types or typeRoots, ... are they merged? how?

This is why I'm totally 👍 for something like Jest has with jest --showConfig, but for tsc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Suggestion An idea for TypeScript
Projects
None yet
Development

No branches or pull requests

3 participants