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 resolution mechanism #2583

Closed
steabert opened this issue Sep 30, 2022 · 2 comments
Closed

tsconfig resolution mechanism #2583

steabert opened this issue Sep 30, 2022 · 2 comments

Comments

@steabert
Copy link

I had a question regarding how esbuild resolves the tsconfig file assiciated with an imported file. I ran into an issue with another tool privatenumber/tsx#96, discovering that esbuild properly handles multiple TypeScript projects.

We wondered how esbuild does this. Does it look for a new tsconfig.json when a new file is imported that is not part of the files already included by the current tsconfig.json file, and then cache that?

@evanw
Copy link
Owner

evanw commented Sep 30, 2022

For a given file, esbuild looks for the closest tsconfig.json file in a parent directories of that file. This behavior is similar to how npm locates the relevant package.json file.

@evanw
Copy link
Owner

evanw commented Dec 4, 2022

I'm closing this issue because this question was answered.

@evanw evanw closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants