ConfigModuleOptions
interface ConfigModuleOptions {
cache?: boolean
isGlobal?: boolean
ignoreEnvFile?: boolean
ignoreEnvVars?: boolean
envFilePath?: string | string[]
encoding?: string
validate?: (config: Record<string, any>) => Record<string, any>
validationSchema?: any
validationOptions?: Record<string, any>
load?: Array<ConfigFactory>
expandVariables?: boolean | DotenvExpandOptions
}
Properties
Property | Description |
---|---|
cache?: boolean
|
If "true", values from the process.env object will be cached in the memory. This improves the overall application performance. See: https://github.com/nodejs/node/issues/3104 |
isGlobal?: boolean
|
If "true", registers |
ignoreEnvFile?: boolean
|
If "true", environment files ( |
ignoreEnvVars?: boolean
|
If "true", predefined environment variables will not be validated. |
envFilePath?: string | string[]
|
Path to the environment file(s) to be loaded. |
encoding?: string
|
Environment file encoding. |
validate?: (config: Record<string, any>) => Record<string, any>
|
Custom function to validate environment variables. It takes an object containing environment variables as input and outputs validated environment variables. If exception is thrown in the function it would prevent the application from bootstrapping. Also, environment variables can be edited through this function, changes will be reflected in the process.env object. |
validationSchema?: any
|
Environment variables validation schema (Joi). |
validationOptions?: Record<string, any>
|
Schema validation options. See: https://joi.dev/api/?v=17.3.0#anyvalidatevalue-options |
load?: Array<ConfigFactory>
|
Array of custom configuration files to be loaded. See: https://docs.nestjs.com/techniques/configuration |
expandVariables?: boolean | DotenvExpandOptions
|
A boolean value indicating the use of expanded variables, or object containing options to pass to dotenv-expand. If .env contains expanded variables, they'll only be parsed if this property is set to true. |