Skip to content
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

tsconfig extend does not deep-clone compilerOptions.types #44597

Closed
tholewebgods opened this issue Jun 15, 2021 · 4 comments
Closed

tsconfig extend does not deep-clone compilerOptions.types #44597

tholewebgods opened this issue Jun 15, 2021 · 4 comments
Labels
Working as Intended The behavior described is the intended behavior; this is not a bug

Comments

@tholewebgods
Copy link

Bug Report

πŸ”Ž Search Terms

extends tsconfig types compilerOptions Cannot find module or its corresponding type declarations svelte

πŸ•— Version & Regression Information

  • Affected version is 4.3.2 and earlier

⏯ Playground Link

Repository with relevant code

πŸ’» Code

MCVE: https://github.com/tholewebgods/typescript-extend-not-deep-clone-mcve

πŸ™ Actual behavior

The compiler does not load modules of a specific type configured via extends config when root config also specifies types.

πŸ™‚ Expected behavior

When extending from configs types shall be merged.

@MartinJohns
Copy link
Contributor

Related: #27098

@RyanCavanaugh RyanCavanaugh added the Working as Intended The behavior described is the intended behavior; this is not a bug label Jun 15, 2021
@RyanCavanaugh
Copy link
Member

This is the intended behavior; if you didn't want to copy down the parent types, you'd have no way of expressing that, whereas today you can at least write what you mean. It'd be a fairly large breaking change in build system to change this now, especially since there'd be no workaround apart from editing the upstream config file (which you'd have no way of tracking down the child dependencies of).

@typescript-bot
Copy link
Collaborator

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

@Exotelis
Copy link

Exotelis commented Sep 8, 2023

@RyanCavanaugh sorry for posting here again, but I also stumbled over this behavior. Wouldn't it make sense to point this out in the documentation then? What else is excluded from inheritance then, is there a document list?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Working as Intended The behavior described is the intended behavior; this is not a bug
Projects
None yet
Development

No branches or pull requests

5 participants