Skip to main content

โš™๏ธ Configs

Use vite.configs.configs when you only want rules that target Vite and Vitest configuration files.

This preset intentionally ignores client-runtime patterns and benchmark organization.

It is the smallest preset that still covers Vite-specific config migrations and unsafe server defaults.

Flat configโ€‹

import vite from "@typpi/eslint-plugin-vite";

export default [vite.configs.configs];

When to use itโ€‹

  • you mainly want config-file guardrails
  • you want to catch deprecated Vite config paths before they spread across packages
  • you want review pressure around dev-server host, CORS, and filesystem safety
  • your project has generated client files that should stay out of scope
  • you want a smaller entry point before enabling broader presets

Rules in this presetโ€‹

RuleFix
vite/config-require-define-configโ€”
vite/no-empty-env-prefixโ€”
vite/no-relative-resolve-aliasโ€”
vite/no-deprecated-config-optionsโ€”
vite/no-unsafe-server-optionsโ€”
vite/no-import-meta-env-in-configโ€”
vite/no-implicit-config-flagsโ€”
vite/no-disabled-vitest-typecheckโ€”
vite/no-zero-vitest-timeoutโ€”
vite/no-unsafe-vitest-flagsโ€”
vite/require-vitest-typecheck-tsconfigโ€”
vite/no-disabled-vitest-isolationโ€”
vite/no-zero-vitest-slow-test-thresholdโ€”
vite/no-pass-with-no-testsโ€”
vite/no-vitest-globalsโ€”
vite/no-empty-vitest-projectsโ€”
vite/no-empty-vitest-includeโ€”
vite/no-empty-vitest-project-nameโ€”
vite/no-empty-vitest-excludeโ€”
vite/no-empty-vitest-bench-includeโ€”
vite/no-empty-vitest-bench-excludeโ€”
vite/no-empty-vitest-coverage-includeโ€”
vite/no-empty-vitest-coverage-reporterโ€”
vite/no-empty-vitest-coverage-reports-directoryโ€”
vite/no-empty-vitest-project-excludeโ€”
vite/no-mixed-defineworkspace-and-test-projectsโ€”
vite/require-vitest-sequence-seed-when-shuffleโ€”
vite/no-vitest-watch-in-configโ€”
vite/no-vitest-ui-in-configโ€”
vite/no-vitest-file-parallelism-disabledโ€”
vite/no-vitest-single-thread-pool-by-defaultโ€”
vite/no-vitest-bail-and-retry-conflictโ€”
vite/no-vitest-max-workers-zeroโ€”
vite/no-vitest-min-workers-greater-than-max-workersโ€”
vite/require-vitest-coverage-provider-when-enabledโ€”
vite/require-vitest-coverage-reporter-when-enabledโ€”
vite/require-vitest-coverage-thresholds-when-enabledโ€”
vite/no-vitest-coverage-enabled-false-with-thresholdsโ€”
vite/no-vitest-coverage-all-falseโ€”
vite/no-vitest-coverage-clean-falseโ€”
vite/no-vitest-coverage-skip-full-false-in-strictโ€”
vite/require-vitest-coverage-reports-directoryโ€”
vite/no-vitest-coverage-reporter-text-onlyโ€”
vite/no-vitest-coverage-temp-dir-in-repo-rootโ€”
vite/require-vitest-mock-reset-policyโ€”
vite/prefer-vitest-restore-mocksโ€”
vite/no-vitest-unstub-globals-falseโ€”
vite/no-vitest-unstub-envs-falseโ€”
vite/no-vitest-env-leakage-comboโ€”
vite/require-vitest-environment-match-globsโ€”
vite/no-empty-optimize-deps-includeโ€”
vite/no-empty-optimize-deps-excludeโ€”
vite/no-empty-ssr-noexternalโ€”
vite/no-empty-ssr-externalโ€”
vite/no-empty-worker-pluginsโ€”