# Env diagnostics

<!-- Generated by docs/modules/diagnostics from the package catalogs. Write a guide in docs/diagnostics/<CODE>.md instead of editing this file. -->

Each Env error has a stable `code`. Its `docs` link opens the page of that code. This page lists all 56 codes, and [All diagnostics](https://vitehub.dev/docs/reference/diagnostics) lists every primitive.

## Runtime errors

| Code | What happened |
| --- | --- |
| [`ENV_R0001`](https://vitehub.dev/docs/env/diagnostics/env_r0001) | See the page of the code. |
| [`ENV_R0002`](https://vitehub.dev/docs/env/diagnostics/env_r0002) | env.source() requires one or more non-empty env variable names. |
| [`ENV_R0003`](https://vitehub.dev/docs/env/diagnostics/env_r0003) | env.provider() requires a provider name that starts with a letter and contains only letters, numbers, underscores, or hyphens. |
| [`ENV_R0004`](https://vitehub.dev/docs/env/diagnostics/env_r0004) | env.provider() requires a non-empty provider key. |
| [`ENV_R0005`](https://vitehub.dev/docs/env/diagnostics/env_r0005) | env() only accepts a single options object. |
| [`ENV_R0006`](https://vitehub.dev/docs/env/diagnostics/env_r0006) | env() does not accept required. A value is required by default. Use optional: true for a value that can be missing. |
| [`ENV_R0008`](https://vitehub.dev/docs/env/diagnostics/env_r0008) | See the page of the code. |
| [`ENV_R0009`](https://vitehub.dev/docs/env/diagnostics/env_r0009) | Server Env at \<path\> uses env.provider(). Use loadServerEnv() or runWithServerEnv(). |
| [`ENV_R0010`](https://vitehub.dev/docs/env/diagnostics/env_r0010) | See the page of the code. |
| [`ENV_R0011`](https://vitehub.dev/docs/env/diagnostics/env_r0011) | See the page of the code. |
| [`ENV_R0012`](https://vitehub.dev/docs/env/diagnostics/env_r0012) | package.json must contain an object. |
| [`ENV_R0013`](https://vitehub.dev/docs/env/diagnostics/env_r0013) | defineEnvProvider() requires a provider with a read({ env, keys, signal }) method. |
| [`ENV_R0014`](https://vitehub.dev/docs/env/diagnostics/env_r0014) | \<label\> uses an async schema. Env validation currently requires sync schemas. |
| [`ENV_R0015`](https://vitehub.dev/docs/env/diagnostics/env_r0015) | Invalid \<label\>: \<issues\> |
| [`ENV_R0016`](https://vitehub.dev/docs/env/diagnostics/env_r0016) | Invalid \<label\>: \<issues\> |
| [`ENV_R0017`](https://vitehub.dev/docs/env/diagnostics/env_r0017) | Invalid \<label\>: \<error\> |
| [`ENV_R0018`](https://vitehub.dev/docs/env/diagnostics/env_r0018) | Invalid \<label\>: \<error\> |
| [`ENV_R0019`](https://vitehub.dev/docs/env/diagnostics/env_r0019) | The configured Server Env provider is unavailable or invalid. |
| [`ENV_R0020`](https://vitehub.dev/docs/env/diagnostics/env_r0020) | Server Env loading was aborted. |
| [`ENV_R0021`](https://vitehub.dev/docs/env/diagnostics/env_r0021) | The Server Env provider was not loaded. |
| [`ENV_R0022`](https://vitehub.dev/docs/env/diagnostics/env_r0022) | env.enum() requires one or more unique non-empty strings. |
| [`ENV_R0023`](https://vitehub.dev/docs/env/diagnostics/env_r0023) | Invalid default for \<path\>: \<message\> |
| [`ENV_R0025`](https://vitehub.dev/docs/env/diagnostics/env_r0025) | --stage requires a name. |
| [`ENV_R0026`](https://vitehub.dev/docs/env/diagnostics/env_r0026) | Unknown option: \<arg\> |
| [`ENV_R0027`](https://vitehub.dev/docs/env/diagnostics/env_r0027) | The selected stage does not configure the Env plugin. |
| [`ENV_R0028`](https://vitehub.dev/docs/env/diagnostics/env_r0028) | inspectServerEnv() returned an invalid result. |
| [`ENV_R0029`](https://vitehub.dev/docs/env/diagnostics/env_r0029) | env.schemaFrom() requires a non-empty module specifier. |
| [`ENV_R0030`](https://vitehub.dev/docs/env/diagnostics/env_r0030) | The SSR environment does not support runnable imports. |
| [`ENV_SEAL_EXPIRED`](https://vitehub.dev/docs/env/diagnostics/env_seal_expired) | The sealed value expired at \<value\>. |
| [`ENV_SEAL_INVALID`](https://vitehub.dev/docs/env/diagnostics/env_seal_invalid) | The string is not a sealed value, someone changed it, or another root secret sealed it. |
| [`ENV_SEAL_SCHEMA_MISMATCH`](https://vitehub.dev/docs/env/diagnostics/env_seal_schema_mismatch) | The sealed value opened, but it does not match `schema`. |
| [`ENV_SEAL_USED_UP`](https://vitehub.dev/docs/env/diagnostics/env_seal_used_up) | The sealed value was read as many times as its `uses` allow, so it is gone. |
| [`ENV_SEAL_WRONG_PURPOSE`](https://vitehub.dev/docs/env/diagnostics/env_seal_wrong_purpose) | The value was sealed for another purpose than "\<purpose\>". |
| [`ENV_SERVICE_TOKEN_INVALID`](https://vitehub.dev/docs/env/diagnostics/env_service_token_invalid) | The request has no `Authorization: Bearer` token that matches a token in `<name>`. |
| [`ENV_SERVICE_TOKEN_UNSET`](https://vitehub.dev/docs/env/diagnostics/env_service_token_unset) | `<name>` has no token on this server, so every request is refused. |
| [`ENV_WEBHOOK_BODY_INVALID`](https://vitehub.dev/docs/env/diagnostics/env_webhook_body_invalid) | The webhook has a valid signature, but its body is not JSON, or a GitHub form delivery has no JSON `payload` field. |
| [`ENV_WEBHOOK_SECRET_UNSET`](https://vitehub.dev/docs/env/diagnostics/env_webhook_secret_unset) | `<name>` has no webhook secret on this server, so every delivery is refused. |
| [`ENV_WEBHOOK_SIGNATURE_INVALID`](https://vitehub.dev/docs/env/diagnostics/env_webhook_signature_invalid) | The `<header>` header is missing, or it does not match the body signed with a secret in `<name>`. |

## Configuration errors

| Code | What happened |
| --- | --- |
| [`ENV_SEAL_ARGUMENT_INVALID`](https://vitehub.dev/docs/env/diagnostics/env_seal_argument_invalid) | See the page of the code. |

## Build errors

| Code | What happened |
| --- | --- |
| [`ENV_B0001`](https://vitehub.dev/docs/env/diagnostics/env_b0001) | Missing resolved Env state for \<projectRoot\> |
| [`ENV_B0002`](https://vitehub.dev/docs/env/diagnostics/env_b0002) | Env provider names must start with a letter and contain only letters, numbers, underscores, or hyphens. |
| [`ENV_B0003`](https://vitehub.dev/docs/env/diagnostics/env_b0003) | Env provider \<name\> requires a non-empty module specifier. |
| [`ENV_B0004`](https://vitehub.dev/docs/env/diagnostics/env_b0004) | Env provider \<name\> uses an unsupported namespaced Windows module path. |
| [`ENV_B0005`](https://vitehub.dev/docs/env/diagnostics/env_b0005) | \<path\> references Env provider \<provider\>, but hubEnv({ providers }) does not configure it. |
| [`ENV_B0006`](https://vitehub.dev/docs/env/diagnostics/env_b0006) | \<file\>:\<line\>\<value\>: \<reason\> |
| [`ENV_B0007`](https://vitehub.dev/docs/env/diagnostics/env_b0007) | Timed out waiting for the generated secret lock: \<secretPath\>.lock |

## Errors

| Code | What happened |
| --- | --- |
| [`ENV_BRIDGE_AUDIT_FAILED`](https://vitehub.dev/docs/env/diagnostics/env_bridge_audit_failed) | See the page of the code. |
| [`ENV_BRIDGE_CONFLICT`](https://vitehub.dev/docs/env/diagnostics/env_bridge_conflict) | See the page of the code. |
| [`ENV_BRIDGE_DENIED`](https://vitehub.dev/docs/env/diagnostics/env_bridge_denied) | See the page of the code. |
| [`ENV_BRIDGE_INVALID`](https://vitehub.dev/docs/env/diagnostics/env_bridge_invalid) | See the page of the code. |
| [`ENV_BRIDGE_MISSING`](https://vitehub.dev/docs/env/diagnostics/env_bridge_missing) | See the page of the code. |
| [`ENV_BRIDGE_OPERATION_FAILED`](https://vitehub.dev/docs/env/diagnostics/env_bridge_operation_failed) | See the page of the code. |
| [`ENV_BRIDGE_UNTRUSTED`](https://vitehub.dev/docs/env/diagnostics/env_bridge_untrusted) | See the page of the code. |
| [`ENV_JSON_SCHEMA_INVALID`](https://vitehub.dev/docs/env/diagnostics/env_json_schema_invalid) | env.json() in env.server runs in the server build, so it cannot take a schema object from the config. Export the schema from a module and pass env.schemaFrom(), for example env.json(env.schemaFrom('./server/env.schema.ts', 'settings')). A schema object works only with mode: 'build'. |
| [`ENV_LIST_ITEM_INVALID`](https://vitehub.dev/docs/env/diagnostics/env_list_item_invalid) | env.list() takes the item parser first, for example env.list(env.number(), { default: [1] }). |
| [`ENV_NOT_GENERATED`](https://vitehub.dev/docs/env/diagnostics/env_not_generated) | `<accessor>()` ran outside a Vite build, so ViteHub did not generate the Env registry that it reads. |

<!-- vitehub-docs:section-links -->
## In this section

- [Overview](https://vitehub.dev/raw/docs/env.md)
- [Get started](https://vitehub.dev/raw/docs/env/get-started.md)
- [Configure](https://vitehub.dev/raw/docs/env/configure.md)
- [Server API](https://vitehub.dev/raw/docs/env/server-api.md)
- [Limits and errors](https://vitehub.dev/raw/docs/env/limits-and-errors.md)
- [Env Bridge](https://vitehub.dev/raw/docs/env/bridge.md)
- [App secret](https://vitehub.dev/raw/docs/env/app-secret.md)
- [Sign and seal values](https://vitehub.dev/raw/docs/env/seal.md)
- [Service tokens](https://vitehub.dev/raw/docs/env/service-tokens.md)
- [Verify webhooks](https://vitehub.dev/raw/docs/env/webhooks.md)

All pages: [llms.txt](https://vitehub.dev/llms.txt)
