docs: add monorepo overrides guide

[fengmk2]

Note

Medium Risk
Low product risk (docs-only content), but CI risk is moderate because the E2E matrix adds a new external fixture that can introduce flaky failures or longer runtimes.

Overview
Adds a new Monorepo guide documenting how to use root vite.config.ts with lint.overrides and fmt.overrides for package-specific rules/options, including examples for splitting override configs into separate files.

Wires the new guide into the docs sidebar and updates the lint/fmt config docs to point monorepo users at the override approach.

Extends ecosystem CI by adding the vite-plus-monorepo-overrides fixture to repo.json and running it in the E2E workflow (vp check --fix + vp run verify).

^{Reviewed by Cursor Bugbot for commit 7597248. Configure here.}

[netlify]

✅ Deploy Preview for viteplus-preview ready!

Name	Link
🔨 Latest commit	0687466
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/6a013cb04c86f40008efd327
😎 Deploy Preview	https://deploy-preview-1535--viteplus-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[fengmk2]

• docs: add monorepo overrides guide #1535 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label auto-merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[fengmk2]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 7597248. Configure here.}

[leaysgur]

I think the document itself looks fine.

I would like to confirm my understanding: we are going to continue always appending -c for vp lint|fmt, right?

In that case:

• #1378 and #1380 will become unnecessary
• Since we cannot force the equivalent of -c on the LSP side, we need to prevent lint/fmt from being written in a non-root vite.config.ts
  • We will cover this with lint rules and avoid modifying the oxapps implementation

Is this correct?

[cpojer]

👍

[fengmk2]

I would like to confirm my understanding: we are going to continue always appending -c for vp lint|fmt, right?

There's no final conclusion yet, but we tend to configure lint and fmt only in the root config and see if this recommended solution can meet the vast majority of needs.

• fix(cli)!: stop injecting -c config so oxlint/oxfmt pick up nested vite.config.ts #1378 and feat(check): support --disable-nested-config flag #1380 will become unnecessary

Yes, after this document PR is merged, I will close these 2 PRs.

• Since we cannot force the equivalent of -c on the LSP side, we need to prevent lint/fmt from being written in a non-root vite.config.ts

  • We will cover this with lint rules and avoid modifying the oxapps implementation

Yes, after our oxlint plugin is merged, new rules will be added to intercept it.