How to handle monorepos?

[cktang88]

Documentation is

• Missing
• Outdated
• Confusing
• Not sure

Explain in Detail

Say I have a monorepo with /frontend and /backend and I want different config for them as well as some shared config.
I see Vite+ can be configured using a single vite.config.ts at the root of your project:

So would I just have a root config and then a config file in each folder that overrides the root configs?

Your Suggestion for Changes

Add docs for nested folders overriding

Relevant Page

No response

Reproduction (Optional)

No response

Steps to reproduce (Optional)

No response

[dotnize]

fwiw I have a monorepo template for TanStack Start that uses Vite+:
https://github.com/mugnavo/tanstarter-plus

From what I've observed so far:

• Each package can have their own vite.config.ts file (in my template /apps/web is a TanStack Start app which uses Vite itself, with its own vite config)
• Each vite config can have their own Run tasks, Vite plugins, and Vite server config (example)
• Overriding lint, fmt, and staged doesn't seem to work for me. Only the root config is used
• No native way to concurrently run multiple tasks yet similar to Turborepo, but there's a PR in Vite Task: feat: concurrent execution with cancellation reporting vite-task#232

[Luzefiru]

Piggybacking on this; there isn't an elegant way to prune dependencies for caching in Dockerfiles with Vite+ compared to Turborepo's turbo prune command.

It would be nice if they could add similar functionality or document the best way to write Dockerfiles to deploy Vite+ monorepo applications.