Possible to provide path to alternative tsconfig file?

[WonderPanda]

I'm wondering if its possible to explicitly configure Vite to use a tsconfig file of my choosing?

I've looked through the docs and can't find any information in the config API for being able to specify this explicitly.

When working with NX dev tools it is standard to compose your TS settings across multiple files with tsconfig.app.json being the actual entry point that matters for serving/building the application. I'd like to be able to update vite to leverage the configuration defined in tsconfig.app.json instead of automatically picking up tsconfig.json

[sampullman]

We're also interested in this feature, currently our vue3 plugin generates a tsconfig.app.json to align with Nx best practices, but I can't find a way to get it picked up by Vite. Sticking with a tsconfig.json works for my projects, but some users may have more advanced use cases that benefit from splitting it up the way Nx suggests.

[EdieLemoine]

I would love for this to be able to work out of the box, but for now I made a small Vite plugin that works around this. It copies your tsconfig.build.json (customizable) to tsconfig.json before the build, and deletes it after.

vite-plugin-custom-tsconfig

[rosskevin]

I also ended up writing a file swapping plugin to fit our needs: https://github.com/alienfast/vite-plugin-tsconfig

• allows a default tsconfig.json, in the end it will be put back in place
• allows specifying workspaces for monorepo packages to be swapped at the same time as the root

We were dealing with failed CI storybook/vite builds only to learn that vite tries to discover the nearest tsconfig.json at the package.json level regardless if one exists. The readme explains more.

Our use case: the tsconfig.json in our monorepos is setup for development with the use of project references and paths. We use tsconfig.build.json in our CI/production build scripts to build without path dependencies. Vite seems to be coded with no knowledge of a multi-environment type of use case.

[mccolljr]

This has been here for a while... any chance of an official response?

[xenobytezero]

I'd also really like a solution of some kind for this.

I have used it previously as a workaround to the fact that VSCode also doesn't let you configure which tsconfig.json to use for it's internal TS server, which creates some problems as I move from Rollup to Vite.

I was planning to use vite.config.mts as my config file, which means that in order to correctly resolve imports etc I need to include it in my base tsconfig.json. This means that when Vite runs it will compile that file along with the rest of my source, dumping it in my dist folder, as well as screwing up my output folder layout, etc.

• I can use rootDir, but it throws up a bunch of warnings doing this that I'd rather not see to not freak out other devs.
• I can't use the plugins mentioned here since I need to keep a real tsconfig in the root for VSCode purposes.

Solutions/thoughts would be useful.

[Shakeskeyboarde]

I haven't tried it, but would setting the Vite esbuild.tsconfig option work?

[FranciscoKloganB]

Esbuild only works for development. Vite should accept tsConfig paths for any environment. :\

[ShGKme]

There is no esbuild.tsconfig option in Vite.

[JannieT]

I got it working using the vite-plugin-dts plugin:

import { defineConfig } from 'vite';
import dts from 'vite-plugin-dts';

export default defineConfig({
 plugins: [
    dts({
      tsconfigPath: 'tsconfig.frontend.json'
    })
  ],
  ...

[ZuBB]

Prod mode fails with this for me