Monorepo

Vite+ works well in a monorepo when the shared tool configuration lives in the workspace root. Put the root defaults in vite.config.ts, then use overrides to apply package-specific lint and format settings.

This is the recommended pattern for shared quality tooling because the root config stays type-safe and composable, while each app or package can still keep its own Vite, Vitest, framework, or runtime files when that is useful.

The examples below come from the runnable vite-plus-monorepo-overrides fixture.

Root Config With Overrides

Use lint.overrides for Oxlint rules that only apply to some packages:

vite.config.ts

import { defineConfig } from 'vite-plus';

export default defineConfig({
  lint: {
    plugins: ['typescript'],
    options: {
      typeAware: true,
      typeCheck: true,
    },
    rules: {
      'no-console': ['error', { allow: ['warn', 'error'] }],
    },
    overrides: [
      {
        files: ['apps/web/**', 'packages/ui/**'],
        plugins: ['typescript', 'react'],
        rules: {
          'react/self-closing-comp': 'error',
        },
      },
      {
        files: ['apps/api/**'],
        env: {
          node: true,
        },
        rules: {
          'no-console': 'off',
        },
      },
      {
        files: ['**/*.test.ts', '**/*.spec.ts'],
        plugins: ['typescript', 'vitest'],
        rules: {
          '@typescript-eslint/no-explicit-any': 'off',
          'vitest/no-disabled-tests': 'error',
        },
      },
    ],
  },
});

Globs are resolved from the root vite.config.ts, so use workspace paths such as apps/web/**, apps/api/**, and packages/ui/**.

TIP

When a lint.overrides entry sets plugins, include the plugins needed for that file group. If you omit plugins, the override uses the base lint.plugins value.

Format Overrides

Use fmt.overrides for file or package-specific Oxfmt options. Formatter overrides put their settings under options:

vite.config.ts

import { defineConfig } from 'vite-plus';

export default defineConfig({
  fmt: {
    singleQuote: true,
    semi: true,
    overrides: [
      {
        files: ['apps/api/**'],
        options: {
          printWidth: 120,
        },
      },
      {
        files: ['**/*.md'],
        options: {
          proseWrap: 'always',
        },
      },
    ],
  },
});

Splitting Config Files

You can still split configuration across your repository. Export normal JavaScript objects from nearby files, import them in the root config, and merge them into the matching override.

tooling/lint/react.ts

import type { OxlintOverride } from 'vite-plus/lint';

export const reactLint = {
  plugins: ['typescript', 'react'],
  rules: {
    'react/self-closing-comp': 'error',
  },
} satisfies Omit<OxlintOverride, 'files'>;

tooling/lint/node.ts

import type { OxlintOverride } from 'vite-plus/lint';

export const nodeLint = {
  env: {
    node: true,
  },
  rules: {
    'no-console': 'off',
  },
} satisfies Omit<OxlintOverride, 'files'>;

vite.config.ts

import { defineConfig } from 'vite-plus';

import { nodeLint } from './tooling/lint/node';
import { reactLint } from './tooling/lint/react';

export default defineConfig({
  lint: {
    plugins: ['typescript'],
    options: {
      typeAware: true,
      typeCheck: true,
    },
    overrides: [
      {
        files: ['apps/web/**', 'packages/ui/**'],
        ...reactLint,
      },
      {
        files: ['apps/api/**'],
        ...nodeLint,
      },
    ],
  },
});

This keeps the behavior centralized while letting each team or package own the pieces of config it needs.

App Commands

The root vite.config.ts is most valuable for shared linting, formatting, staged checks, and task definitions. For project-specific development, build, and test behavior, use the setup that best matches each app:

• Pass a folder to built-in Vite commands when you want to target one app:

vp dev apps/web
vp build apps/web

• Keep package-specific scripts in each package when the command differs per app:

apps/api/package.json

{
  "scripts": {
    "dev": "tsx watch src/index.ts",
    "build": "tsc -p tsconfig.json"
  }
}

• Run scripts across the workspace with vp run:

vp run -r build
vp run -r --parallel dev
vp run --filter ./apps/web build

See the Run guide for recursive, parallel, filtered, and cached workspace tasks.