7 declarations
(config: EnvVarConfig<any>, visibility: EnvVisibility): boolean import {env_var_has_visibility} from '@fuzdev/gro/env.js'; Whether a declared env var belongs to visibility - SvelteKit's vars are private
unless declared public: true.
configEnvVarConfig<any>visibilityboolean EnvVarDeclarations import type {EnvVarDeclarations} from '@fuzdev/gro/env.js'; The variables a project's src/env.ts exports via SvelteKit's defineEnvVars.
[key: string]type EnvVarConfig<any>
EnvVisibility type "public" | "private"
import type {EnvVisibility} from '@fuzdev/gro/env.js'; (dev: boolean, env_dir?: string | undefined, env_files?: string[], ambient_env?: Record<string, string | undefined>): Record<string, string> import {load_env} from '@fuzdev/gro/env.js'; Loads every env var from the env files plus the ambient env, later sources winning, so the ambient env overrides the files.
devpicks the development or production mode files for the default env_files
booleanenv_dir?the directory the env files are resolved against, defaults to the cwd
stringenv_filesthe env files to load, in order, defaults to the same files as Vite
string[]to_default_env_files(dev)ambient_envthe env merged in last
Record<string, string | undefined>process.envRecord<string, string>
all loaded vars, unfiltered - resolve_env_vars picks out the declared ones
(key: string, paths?: string[]): string | undefined import {load_from_env} from '@fuzdev/gro/env.js'; Loads a single env value without merging it into process.env.
By default searches process.env, then a local .env if one exists, then ../.env if it exists.
Empty strings are semantically the same as undefined for more ergonomic fallbacks.
keystringpathsstring[]['.env', '../.env']string | undefined
(variables: EnvVarDeclarations, visibility: EnvVisibility, env: Record<string, string | undefined>): Record<string, unknown> import {resolve_env_vars} from '@fuzdev/gro/env.js'; Resolves the declared env vars of one visibility from env, validating each the way
SvelteKit does: a var with no schema must be present, and one with a schema gets its
Standard Schema result, so validators can transform values and make them optional.
variablesthe declarations from the project's src/env.ts
visibilitywhich of the declared vars to resolve
envthe values to resolve them from, usually from load_env
Record<string, string | undefined>Record<string, unknown>
the resolved values keyed by var name
listing - every invalid var, so a misconfigured env fails all at once(dev: boolean): string[] import {to_default_env_files} from '@fuzdev/gro/env.js'; The env files Vite loads for a mode, in precedence order, later files winning.
devbooleanstring[]