tsconfig noEmit error: Cannot reference tsconfig if it extends other tsconfig.

[ekhodx]

Bug Report

🔎 Search Terms

• tsconfig.json
• noEmit
• extends
• reference
• Referenced project may not disable emit.

🕗 Version & Regression Information

Tried 4.8.0-beta, 4.7.3, 4.7.4, and 4.6.3

⏯ Playground Link

💻 Code

Couldn't reproduce this in Bug Workbench, but here is my minimal reproduction repo:
https://github.com/ZerdoX-x-issue-reproducer/microsoft-TypeScript-49844

tsconfig.json:

{
  "references": [{ "path": "./tsconfig.test.json" }],
  "compilerOptions": {
    "noEmit": true
  }
}

tsconfig.test.json:

{
  "extends": "./tsconfig.base.json",
  "compilerOptions": {
    "composite": true,
    "noEmit": true
  }
}

tsconfig.base.json:

{
  "include": [
    "src/**/*.d.ts",
    "src/**/*.js",
    "src/**/*.ts",
  ],
  "compilerOptions": {
    "noEmit": true,
  }
}

🙁 Actual behavior

🙂 Expected behavior

🤔 Other info

SO question

UPDATE: Since this issue keeps receiving comments and attention, I would like to let you know that I don't suffer from this issue anymore, but reproduction will be opened as long as my account exists :) Afair I was using SvelteKit and I just wanted to get proper type checking for all of my files: 1) source files which would or would not get bundled to be running on client and/or server 2) configuration files, where some files use ESM, some still support only CJS 3) tests.
In newer projects I achieve this goal and do not stumble upon this issue, also it got easier now since new ESLint flat config which will be released in next major release.

[Markkos89]

facing the same issue and is driving me crazy :(

[ekhodx]

facing the same issue and is driving me crazy :(

For me it doesn't affect anything. Just a visual error in vscode, so it's fair enough to place a comment with linking this issue above "references": (glad typescript.json is JSONC) and ignore it without remorse.

[RyanCavanaugh]

This configuration doesn't make any sense; every behavior of having a reference is dependent on the output files of the referenced project being present. What are you trying to achieve?

[Josh-Cena]

Question: is there an easy way to type-check with a single tsc run, without emit, and with different sets of files using different libs? Or do we have to use multiple tsc runs?

[RyanCavanaugh]

Question: is there an easy way to type-check with a single tsc run, without emit, and with different sets of files using different libs

No

[ekhodx]

This configuration doesn't make any sense; every behavior of having a reference is dependent on the output files of the referenced project being present. What are you trying to achieve?

Of course this configuration doesn't make any sense. Because this is not a configuration but a minimal reproduction of the issue. If you need to see my full production setup, I've added all configs to the my-full-configuration folder.

[RyanCavanaugh]

That doesn't really answer my question, I guess.

Referencing a project does the following:

• Changes imports of .ts files to their corresponding .d.ts files (under noEmit, those .d.ts files don't exist)
• Causes tsc -b to rebuild the upstream project if it's out of date (if it doesn't emit, this question doesn't make any sense)
• Adds any declaration outFile to the current project (under noEmit, those .d.ts files don't exist)

[ekhodx]

If I don't reference tsconfig.test.json in tsconfig.json I will end up with errors like this while trying to import from $lib (alias is set in tsconfig.base.json which is inherited in tsconfig.test.json) in files which are excluded in tsconfig.json

And also I noticed that vscode says I don't have tsconfig loaded for this file (and that's the reason why aliases doesn't work). Is this an issue with vscode?

But when I do reference, vscode shows loaded tsconfig.test.json as expected for this file.

[typescript-bot]

This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

[ekhodx]

Nice.

[tylim88]

add

"include": [],
"files":[]

in base config get rid of the error message