Configuring Vite+

Vite+ keeps project configuration in one place: vite.config.ts, allowing you to consolidate many top-level configuration files in a single file. You can keep using your Vite configuration such as server or build, and add Vite+ blocks for the rest of your workflow:

vite.config.ts

import { defineConfig } from 'vite-plus';

export default defineConfig({
  server: {},
  build: {},
  preview: {},

  create: {},
  run: {},
  fmt: {},
  lint: {},
  check: {},
  test: {},
  pack: {},
  staged: {},
});

Vite+ Specific Configuration

Vite+ extends the basic Vite configuration with these additions:

• create for project and template scaffolding defaults
• run for Vite Task
• fmt for Oxfmt
• lint for Oxlint
• check for vp check defaults
• test for Vitest
• pack for tsdown
• staged for staged-file checks
• defaultPackage for the default target of bare app commands at a workspace root

defaultPackage

Default target directory for vp dev / vp build / vp preview / vp pack when you invoke them bare in the directory containing the config, an implicit vp -C <dir>:

vite.config.ts

export default {
  defaultPackage: './frontend',
};

vp reads the values without executing the config, so defaultPackage also works at repository roots with no vite-plus dependency (for example a Laravel or Rails repo whose Vite app lives in frontend/, with vite-plus installed only there). That static read is why the values must stay plain string literals rather than expressions. An explicit -C or positional target always wins over the config.