You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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 currenttsconfig.json
file, and then cache that?The text was updated successfully, but these errors were encountered: