Client code reads non-public names
API_TOKEN
Vite env prefix preflight
Check VITE_ public env boundaries before a client build.
Paste env key names and import.meta.env references. The checker reports names only: missing references, non-public client reads, public secret-like names, and mode boundary reminders.
Vite snippets
Names onlyDo not paste env values, tokens, service role keys, deployment logs, or full source files. This page checks static names and public-prefix boundaries only.
Preflight result
fail
Vite env references need prefix or exposure review before the client build.
Env names3
References3
Missing0
Public secrets0
Boundary to review
Client code references env names without the VITE_ prefix.
Boundary to review
Non-VITE_ env names can stay server/build-only, but browser code cannot read them through import.meta.env.
Detected names
Client references
- API_TOKEN
- MODE
- VITE_API_BASE_URL
Server/build-only names
- API_TOKEN
What this checks
It checks static Vite env names, `VITE_` client exposure, built-in names like MODE and PROD, missing references, and public secret-like naming before a build.
What this does not do
It does not run Vite, read your project files, inspect deployment settings, evaluate mode loading order, or prove that a value exists in production.