Root @decorators

Root decorators appear in the header section of a .env file - which is any comment block(s) at the beginning of the file, before the first config item. Usually root decorators are used only in your .env.schema file.

.env.schema

# This is the header, it can contain root decorators
# @defaultSensitive=false @defaultRequired=infer
# @generateTsTypes(path=./env.d.ts)

More details of the minutiae of decorator handling can be found in the @env-spec reference.

General root decorators

These are the root decorators that are built into Varlock. Plugins may introduce more.

@currentEnv

Value type: ref() (usually written as $ITEM_NAME)

Sets the current environment value, which will be used when determining if environment-specific .env files will be loaded (e.g. .env.production), and also may affect other dynamic behaviour in your schema, such as the forEnv() function. We refer to the name of this item as your environment flag.

• It must be set to a simple reference to a single config item (e.g. $APP_ENV).
• This decorator should only be set in your .env.schema file.
• The referenced item must be defined within the same file.
• This will override the --env CLI flag if it is set.
• We do not recommend using NODE_ENV as your environment flag, as it has other implications, and is often set out of your control.

See environments guide for more info.

# @currentEnv=$APP_ENV
# ---
# @type=enum(dev, preview, prod, test)
APP_ENV=dev

@envFlag (deprecated)

Value type: string (must be a valid item name within same file)

Sets the current environment flag by name.

⚠️ Deprecated at v0.1 - use @currentEnv instead.

@envFlag=APP_ENV -> @currentEnv=$APP_ENV

@defaultRequired

Value type: boolean | "infer"

Sets the default behavior of each item being required. Only applied to items that have a definition within the same file. Can be overridden on individual items using @required/@optional.

• infer (default): Items with a value set in the same file will be required; items with an empty string or no value are optional.
• true: All items are required unless marked optional.
• false: All items are optional unless marked required.

# @defaultRequired=infer
# ---

FOO=bar        # required (static value)
BAR=fnCall()   # required (function value)
BAZ=           # optional (no value)
QUX=''         # optional (empty string)

# @optional
OPTIONAL_ITEM=foo # optional (explicit)

# @required
REQUIRED_ITEM= # required (explicit)

@defaultSensitive

Value type: boolean | inferFromPrefix(PREFIX)

Sets the default state of each item being treated as sensitive. Only applied to items that have a definition within the same file. Can be overridden on individual items using @sensitive.

• true (default): All items are sensitive unless marked otherwise.
• false: All items are not sensitive unless marked otherwise.
• inferFromPrefix(PREFIX): Item is marked not sensitive if key starts with the given PREFIX; all others are sensitive. Useful for marking e.g. PUBLIC_ keys as non-sensitive by default.

📖 See the secrets management guide for best practices on handling sensitive values, and how to use plugins to fetch them from secret management platforms.

# @defaultSensitive=inferFromPrefix(PUBLIC_)
# ---

PUBLIC_FOO= # not sensitive (due to matching prefix)
OTHER_FOO=  # sensitive (default when prefix does not match)

# @sensitive
PUBLIC_BAR= # sensitive (explicit decorator overrides prefix)
# @sensitive=false
OTHER_BAR=  # not sensitive (explicit)

@disable

Value type: boolean

If true, disables loading the file - meaning no items or plugins are loaded from it. Useful for temporarily or conditionally disabling a .env file.

💡 The forEnv() function can disable an explicitly imported file based on the current environment.

# @disable  # (shorthand for @disable=true)
#
# @plugin(@varlock/x-plugin)  # will not be loaded
# ---
FOO=bar  # will be ignored

@import()

Arg types: [ path: string ]
Named args: enabled?: boolean, allowMissing?: boolean, pick?: string[], omit?: string[]

Imports other .env file(s) - useful for sharing config across monorepos and splitting up large schemas. Can be called multiple times.

You may import a specific file, or a directory of files. Importing a directory (trailing /) brings everything that directory would load on its own (its .env.schema plus sibling .env, .env.local, and environment-specific files, resolved by the current environment flag), whereas importing a single file brings only that file. To pull in a sibling or root package’s values (not just its schema), import the directory.

The optional enabled parameter allows conditional imports based on boolean expressions. It defaults to true if not specified.

The optional allowMissing parameter makes the import optional - if set to true, the import will be silently skipped if the file or directory doesn’t exist instead of causing a loading error. It defaults to false if not specified.

Filtering keys: by default every key from the imported file(s) is brought in. Use pick to import only an allowlist of keys, or omit to import everything except a denylist. You can’t use both in one import, and both accept simple globs (*, ?). Across nested imports, filters intersect: a key must pass every filter in the chain.

Positional keys are deprecated

Listing keys as positional args (@import(./.env.other, KEY1, KEY2)) is deprecated; use pick=[KEY1, KEY2] instead. The positional form still works (exact-match only, no globs) but will warn.

See the imports guide for more details and advanced usage.

# @import(./.env.imported)                        # import a specific file
# @import(./.env.other, pick=[KEY1, KEY2])        # import only these keys (allowlist)
# @import(./.env.other, pick=[API_*])             # globs are supported
# @import(./.env.other, omit=[SECRET])            # import everything except these (denylist)
# @import(../shared-env/)                         # import a directory
# @import(~/.env.shared)                          # import from home directory
# @import(./.env.dev, enabled=eq($ENV, "dev"))    # conditional import
# @import(./.env.local, allowMissing=true)        # optional import (no error if missing)
# ---

# this definition is merged with any found in imports, but this one has more precedence
IMPORTED_ITEM=overridden-value

@setValuesBulk()

Arg types: [ data: string ] Named args: format?: "json" | "env", createMissing?: boolean, enabled?: boolean, pick?: string[], omit?: string[]

Injects multiple config values at once from an external data source. The first argument is a resolver that produces a string, typically a bulk resolver from a secrets provider plugin such as opLoadEnvironment() (1Password), infisicalBulk(), or vaultSecret(…, raw=true) (HashiCorp Vault). The string is parsed and injected as definitions within the file containing the decorator.

Bulk values participate in the normal file override chain: process.env still overrides everything, higher-precedence files (.env.local, .env.production, etc.) override bulk values, and bulk values override schema-defined defaults in the same file. You control precedence by choosing which file to put @setValuesBulk in.

Options:

• format: How to parse the data string. json expects a flat JSON object, env expects .env file format. If not specified, auto-detected by checking if the string starts with {.
• createMissing: If true, keys in the bulk data that don’t already exist in your schema will be created as new config items. Defaults to false (unknown keys are silently skipped).
• enabled: If false, the bulk data resolver is skipped entirely. Accepts any boolean expression, including dynamic references to other config items. Defaults to true.
• pick: An array of key names to inject, an allowlist. Only matching keys are injected; everything else from the source is ignored.
• omit: An array of key names to skip, a denylist. Every key except the matches is injected.

By default (neither pick nor omit) every key from the source is injected. You can’t use pick and omit together. Both accept simple glob patterns: * matches any run of characters and ? matches a single character (e.g. pick=[API_*]).

Can be called multiple times; later calls overwrite earlier ones for the same keys.

.env.schema

# Load all values from a 1Password environment
# @plugin(@varlock/1password-plugin)
# @initOp(token=$OP_TOKEN, allowAppAuth=forEnv(dev))
# @setValuesBulk(opLoadEnvironment(your-environment-id))
# ---
# @type=opServiceAccountToken @sensitive
OP_TOKEN=
API_KEY=
DB_PASSWORD=

.env.schema

# Inject from a .env-style blob stored in a single 1Password field
# @setValuesBulk(op("op://vault/app-secrets/dotenv"), format=env)
# ---
API_KEY=
DB_PASSWORD=

.env.schema

# Allowlist: only inject these keys (globs allowed, e.g. API_*)
# @setValuesBulk(opLoadEnvironment(your-environment-id), pick=[API_KEY, DB_PASSWORD])
# ---
API_KEY=
DB_PASSWORD=

.env.schema

# Denylist: inject everything except these keys
# @setValuesBulk(infisicalBulk(), omit=[LEGACY_TOKEN, DEBUG_*])

.env.schema

# Create items not already in the schema
# @setValuesBulk(infisicalBulk(), createMissing=true)

.env.schema

# Only fetch from the source in non-production environments
# @setValuesBulk(opLoadEnvironment(dev-environment-id), enabled=eq($APP_ENV, "dev"))
# ---
API_KEY=
APP_ENV=dev

If a plugin doesn’t exist for your provider, any CLI tool works via exec(), e.g. @setValuesBulk(exec("my-secrets-cli export --format=json"), format=json).

Note

When using format=env, function calls like $VAR references in unquoted values are not supported and will cause an error. Use single quotes for literal $ signs (e.g., '$LITERAL') or use format=json instead.

createMissing and type generation

Items created via createMissing=true (those that don’t already exist in your schema) will not be included in generated TypeScript types. Type generation happens at build/schema-load time before values are fetched, so dynamically created keys are invisible to the type generator.

For this reason, createMissing=true is not recommended. Instead, declare all expected items explicitly in your schema (with an empty value) so they are known at type-generation time.

@plugin()

Arg types: [ identifier: string ]

Loads a plugin, which can register new root decorators, item decorators, and resolver functions. Can be called multiple times.

See plugins guide for more details.

# @plugin(@varlock/1password-plugin)
# @initOp(allowAppAuth=true) # new root decorator
# ---
# @type=opServiceAccountToken # new data type
OP_TOKEN=
# @sensitive
XYZ_API_KEY=op(op://api-prod/xyz/api-key) # new resolver

@cache

Value type: "auto" | "memory" | "disk" | "disabled"

Sets global cache mode for cache() and plugin cache APIs.

Modes:

• memory: cache only in-process (not persisted)
• disk: cache to encrypted disk storage (persists across invocations)
• disabled: disable caching globally
• auto (default): uses disk when a native encryption backend is available outside CI; otherwise uses disk encrypted with _VARLOCK_CACHE_KEY if that env var is set, falling back to memory (see the Caching guide)

The value can also be set dynamically with a function, for example to change cache mode per environment. A function that resolves to no value falls back to auto.

# @cache=memory
# ---
SESSION_SECRET=cache(randomHex(32))

# dynamic - only use disk caching in development
# @cache=forEnv(dev, "disk")
# ---

Note

--skip-cache on varlock load / varlock run / varlock printenv disables cache reads and writes for that invocation, regardless of @cache.

See the Caching guide for mode selection guidance by environment.

@redactLogs

Value type: boolean

Controls whether sensitive config values are automatically redacted from console output. When enabled, any sensitive values will be replaced with ▒▒▒▒▒ in logs.

Only applies in JavaScript based projects where varlock runtime code is imported.

• true (default): Console logs are automatically redacted
• false: Console logs are not redacted (useful for debugging)

# @redactLogs=false
# ---
SECRET_KEY=my-secret-value # @sensitive

console.log(process.env.SECRET_KEY)
// This will log "my▒▒▒▒▒" instead of "my-secret-value" when @redactLogs=true

Caution

There is a potential performance impact for both @preventLeaks and @redactLogs when enabled. It depends on the integration and how your application is served. Please reach out if you have any questions.

We feel that they are beneficial enough to have them on by default but you can always opt out if you prefer.

@preventLeaks

Value type: boolean

Controls whether leak prevention is enabled. When enabled, varlock will scan outgoing HTTP responses to detect if sensitive values are being leaked.

Only applies in JavaScript based projects where varlock runtime code is imported.

Options:

• true (default): Leak detection is enabled
• false: Leak detection is disabled (useful for debugging)

# @preventLeaks=false
# ---
SECRET_KEY=my-secret-value # @sensitive

To opt out leak detection for a single item (for example a secret an endpoint legitimately returns to another system) while keeping it enabled everywhere else, use the @sensitive options form: @sensitive={preventLeaks=false}. The value is still redacted in logs.

a sample leak detection warning in an Astro project

Caution

See note on @redactLogs about potential performance impact.

@encryptInjectedEnv

Value type: boolean

Controls whether the injected env blob in server-side build output is encrypted. When enabled, varlock encrypts the blob with AES-256-GCM using the _VARLOCK_ENV_KEY environment variable.

This is primarily relevant for serverless deployments (Vercel, Netlify, etc.) where varlock injects resolved env data into the build output. The blob only appears in server-side code and is generally safe, but encryption provides extra protection, particularly against secrets leaking via sourcemaps.

Options:

• false (default): Blob is injected as plaintext JSON
• true: Blob is encrypted, _VARLOCK_ENV_KEY required at build time and runtime
• forEnv(...): Conditionally enable based on the current environment

# @encryptInjectedEnv
# ---
SECRET_KEY= # @sensitive

# only encrypt in production
# @encryptInjectedEnv=forEnv(prod)
# ---
SECRET_KEY= # @sensitive

Key management:

• For Cloudflare Workers, the key is auto-generated and uploaded as a secret binding, so no manual setup is needed
• For local dev, a temporary key is auto-generated when running dev servers
• For production deploys to other platforms, you must set _VARLOCK_ENV_KEY on your platform (see the encrypted deployments guide)

@disableProcessEnvInjection

Value type: boolean

Prevents varlock from injecting resolved values into process.env. When enabled, env vars are only accessible via the ENV proxy; process.env.MY_VAR will not contain varlock-resolved values.

This is useful for security hardening. Combined with @encryptInjectedEnv, it ensures that no plaintext secrets exist in process.env at all.

When set, @generateTsTypes stops augmenting process.env by default (its processEnv option defaults to none), so your generated types match the fact that process.env isn’t populated.

Options:

• false (default): Values are injected into process.env as usual
• true: Values are only accessible via ENV

The value must be static (true/false). Because code generation reads this flag, an environment-dependent value would make generated output differ per environment.

# @disableProcessEnvInjection
# ---
SECRET_KEY= # @sensitive
PUBLIC_URL=

Caution

When enabled, any code that reads from process.env directly (including third-party libraries) will not see varlock-resolved values. Make sure all env access in your application goes through the ENV proxy.

Note

This decorator only affects the runtime initVarlockEnv() behavior. It does not affect varlock run, which always injects individual env vars into the child process by default. Use varlock run --no-inject-vars if you also want to skip individual var injection when using varlock run.

@auditIgnorePaths()

Arg types: [ ...paths: string[] ]

Excludes directories from the varlock audit code scanner. Paths are relative to the file containing the decorator. Can be called multiple times; paths are merged additively.

Useful for excluding generated code, vendored dependencies, or directories that contain env var references you don’t want to audit.

# @auditIgnorePaths(vendor, generated/config)
# ---
API_KEY=

# called multiple times, paths are merged
# @auditIgnorePaths(vendor)
# @auditIgnorePaths(generated/config, scripts/setup)
# ---
API_KEY=

Code generation

Code-generation decorators turn your schema into generated code, such as TypeScript type declarations or ready-to-use env modules for other languages, and plugins can register generators that emit other kinds of code. See the Code generation guide for the full picture, and Other languages for per-language usage.

Every @generate* decorator below is a root decorator that can be called multiple times (one per output file) and shares these common args:

• path: Relative filepath to write the generated file to.
• auto: Controls whether generation runs automatically on every load (defaults to true). Set to false to generate only when you run varlock codegen explicitly, useful in a CI pipeline or a dedicated build step.
• executeWhenImported: overrides the default of not executing when the containing file is imported (defaults to false).
• filter: Restrict this generated file to a subset of items, using the same selector language as the CLI --filter flag: key names/globs, !negations, @sensitive/@required, and #tagname (set via @tag()). Quote the value if it has more than one comma-separated selector (the decorator parser splits args on unquoted commas), e.g. filter="STRIPE_*,!STRIPE_DEBUG_KEY". Call the same decorator multiple times with different path/filter pairs to emit several subset files from one schema.

# only ship billing-tagged keys to the billing package's generated types
# @generateTsTypes(path=./billing/env.d.ts, filter=#billing)

Tip

Usually these decorators live in your primary .env.schema file, and are ignored within imported files. To override this, set executeWhenImported to true.

@generateTsTypes()

TypeScript type declarations. Makes import { ENV } from 'varlock/env' typed and augments process.env / import.meta.env. In addition to the common code-generation args, it accepts:

• exposeEnv: where the coerced ENV object lives (defaults to global).
  • global: globally augment varlock/env so import { ENV } from 'varlock/env' is typed.
  • local: export a package-local typed ENV from the generated file (with no global augmentation, since processEnv/importMetaEnv default to none too, so nothing merges across packages). Use this in monorepos where multiple packages have different schemas. Requires a .ts output path (not .d.ts, since it contains a runtime re-export), and you import from the generated file (e.g. import { ENV } from './env').
  • none: emit only the type definitions, no ENV binding.
• processEnv: how process.env is typed: strict, loose, or none (defaults to strict; to none when exposeEnv=local, or when @disableProcessEnvInjection is set, since values aren’t put on process.env then). Note that @types/node declares a base string index signature that can’t be removed, so extra keys remain allowed on process.env regardless.
• importMetaEnv: how import.meta.env is typed: strict, loose, or none (defaults to strict; to none when exposeEnv=local).

# @generateTsTypes(path=./env.d.ts)
# monorepo-friendly: importable local ENV, no globals
# @generateTsTypes(path=./env.ts, exposeEnv=local)

@generatePythonEnv()

A self-contained Python module: a coerced Env TypedDict, a load_env() that parses the injected env, and a SENSITIVE_KEYS constant. See Python usage.

# @generatePythonEnv(path=./env.py)

@generateRustEnv()

A self-contained Rust module: a serde-derived Env struct, a load() function, and a SENSITIVE_KEYS constant. Requires the serde and serde_json crates. See Rust usage.

# @generateRustEnv(path=./src/env.rs)

@generateGoEnv()

A self-contained Go package: an Env struct, a Load() function, and a SensitiveKeys map. See Go usage.

# @generateGoEnv(path=./env/env.go)

The package name defaults to the output directory (e.g. path=env/env.go → package env); override it with package=.

@generatePhpEnv()

A self-contained PHP class: a readonly Env with a static load() and a SENSITIVE_KEYS constant. Requires PHP 8.1+. See PHP usage.

# @generatePhpEnv(path=./Env.php)

Defaults to a global final class Env. For Composer/PSR-4 projects, set namespace= and/or class= (e.g. @generatePhpEnv(path=src/Env.php, namespace="App\\Config", class=AppEnv)).

@generateTypes() (deprecated)

Deprecated TypeScript-only alias for @generateTsTypes. @generateTypes(lang=ts, path=...) still works; for other languages use the matching @generate*Env decorator (@generateTypes(lang=py, ...) errors with a pointer to @generatePythonEnv).