Add support for specified tsconfig file

[ylc395]

Description

There is no way to specify a tsconfig file for vite now.

See related Discussions:

#8483
#4333
#3939

Suggested solution

Provide a field named tsconfig in esbuild field of vite config.

Basically, we can pass this field to here:

vite/packages/vite/src/node/plugins/esbuild.ts

Line 110 in 8d0a9c1

const loadedTsconfig = await loadTsconfigJsonForFile(filename)

Alternative

No response

Additional context

I'm glad to implement this feature.

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[sapphi-red]

I think there's already tsconfigRaw property.
https://stackblitz.com/edit/vitejs-vite-in7pn4?file=vite.config.js&terminal=dev

[ylc395]

Yes. But what if we prefer config file, especially using extends?

[sapphi-red]

In that case, using tsconfck will work as a workaround.

[EdieLemoine]

I made another workaround, a small Vite plugin that copies your other tsconfig to tsconfig.json before the build, and removes it after. It's vite-plugin-custom-tsconfig

[ghost]

I'd like to specify the tsconfig.json file vite should use (and I also expect it to be watched for changes).

We have 2 files:

1. tsconfig.build.json which is used for creating builds with lax error checking.
2. tsconfig.json which is used by IDEs (some of which we can't configure, which is another problem) and default for some tools; it has strict error checking (vite shows errors with this, because our codebase is not ready for strict checking yet.. which is why we want warnings in our IDEs, but not during builds).

I think there's already tsconfigRaw property. https://stackblitz.com/edit/vitejs-vite-in7pn4?file=vite.config.js&terminal=dev

I'm using this workaround right now.
However, it does feel very hacky.

For example, changes to tsconfig.json will not trigger a rebuild (although to be fair, this is complicated further by tsconfig.json "extends" option etc.).

In that case, using tsconfck will work as a workaround.

Even after reading the tsconfck README, I'm not sure how to do this?

I made another workaround, a small Vite plugin that copies your other tsconfig to tsconfig.json before the build, and removes it after. It's vite-plugin-custom-tsconfig

This seems very dangerous, I'd imagine this could break in a number of scenarios.

---

I feel it is the responsibility of vite to load (and watch) tsconfig from a specified path and passing it to esbuild in tsconfigRaw.

• vite using esbuild transform, which is filesystem-independent by design (tsconfig option only allowed for Build, but not for Transform evanw/esbuild#3171 (comment))
• vite does already have code to find, watch and load tsconfig.json