Allow overrides in tsconfig
<!-- π¨ STOP π¨ π¦π§π’π£ π¨ πΊπ»πΆπ· π¨ Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ --> ## Search Terms <!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily --> - tsconfig - overrides - eslint - glob ## Suggestion <!-- A summary of what you'd like to see added or changed --> It would be nice if `tsconfig.json` files would allow an `overrides` section which works in the same way [as ESLint](https://eslint.org/docs/user-guide/configuring#configuration-based-on-glob-patterns). Here I have just one config file in my root for all kind of files and use cases. TypeScript currently needs multiple `tsconfig.json` files. ## Use Cases <!-- What do you want to use this for? What shortcomings exist with current approaches? --> As far as I know editors like VS Code look for the nearest `tsconfig.json` for proper TypeScript support. This make it hard to properly type files which are used for different environments (e.g. source code vs tests vs storybook examples and so on) in the same directory, which seems to be a common convention nowadays (e.g. `src/file.ts`, `src/file.test.ts
Posted by donaldpipowitch on Sep 13, 2019, 6:34 AM
Tags
Related issues
- [BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) β uninstalling the KB fixe
- Feature Request: Auto-resume CLI session when usage limit resets
- Please deobfuscate the Python
- [Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
- # 233 Developers Discussed Abandoning the Office Add-in Platform β An Open Letter on the Office.js Stability, Security & Trust Crisis
- [FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
reliability (Software)
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) β uninstalling the KB fixe
Feature Request: Auto-resume CLI session when usage limit resets
Please deobfuscate the Python
[Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
# 233 Developers Discussed Abandoning the Office Add-in Platform β An Open Letter on the Office.js Stability, Security & Trust Crisis
[FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Admin Materials and Surfaces
AMD Support
Allow overrides in tsconfig
<!-- π¨ STOP π¨ π¦π§π’π£ π¨ πΊπ»πΆπ· π¨ Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ --> ## Search Terms <!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily --> - tsconfig - overrides - eslint - glob ## Suggestion <!-- A summary of what you'd like to see added or changed --> It would be nice if `tsconfig.json` files would allow an `overrides` section which works in the same way [as ESLint](https://eslint.org/docs/user-guide/configuring#configuration-based-on-glob-patterns). Here I have just one config file in my root for all kind of files and use cases. TypeScript currently needs multiple `tsconfig.json` files. ## Use Cases <!-- What do you want to use this for? What shortcomings exist with current approaches? --> As far as I know editors like VS Code look for the nearest `tsconfig.json` for proper TypeScript support. This make it hard to properly type files which are used for different environments (e.g. source code vs tests vs storybook examples and so on) in the same directory, which seems to be a common convention nowadays (e.g. `src/file.ts`, `src/file.test.ts
Comments (0)
No comments yet. Start the discussion.