Nested lint and format configs: share your use cases

[liangmiQwQ]

Vite+ currently reads lint and format settings from the root vite.config.ts, with lint.overrides and fmt.overrides for file- or package-specific settings. Nested lint and format configs are not currently supported.

We're holding off on adding support for now. Some of the factors we're considering are implicit config discovery, configuration semantics, the context AI agents need to understand which settings apply, and the potential performance cost of finding and loading multiple configs. At the same time, we recognize that keeping package-specific context close to the code may have benefits.

The use cases we've heard so far haven't given us a strong enough reason to commit to those semantics. Waiting leaves room to add support later, and we'd like to hear why your project needs nested configs, especially where root-level overrides fall short.

Do you need nested lint or format configs? Tell us why.

It would help to hear:

• What problem would nested configs solve in your project?
• Where do root-level overrides or explicitly importing configuration objects become insufficient or awkward?
• Can you share a concrete example, such as your repository structure and the settings you'd want to keep in individual packages?

If the current approach works well for you, we'd like to hear that too. You don't need to propose an implementation—we're mainly interested in understanding your workflow and the reasons behind your preference.