Vite · VITE0012

Prefer direct import.meta.env access

Finds Vite env code that should use the supported direct import meta env access pattern instead.

VITE0012vite-doctor/viteconfigurationinfoNo fix

vite/env/prefer-direct-import-meta-env-accesssrc/rule-packs/vite/rules/env.ts Upstream docs

Run this rule

pnpm vite-doctor . --framework vite --extends auto,vite/strict --rules vite/env/prefer-direct-import-meta-env-access

Direct import.meta.env.KEY access lets Vite statically replace known values and tree-shake branches; aliasing the whole object obscures those keys.

Use the Vite-supported direct import meta env access pattern instead.

Before

const env = import.meta.env
const apiBase = env.VITE_API_BASE

After

const apiBase = import.meta.env.VITE_API_BASE