$env/dynamic/private

This module provides access to environment variables set dynamically at runtime and that are limited to private access.

Dynamic environment variables are defined by the platform you're running on. For example if you're using adapter-node (or running vite preview), this is equivalent to process.env.

Private access:

• This module cannot be imported into client-side code
• This module includes variables that do not begin with config.kit.env.publicPrefix and do start with config.kit.env.privatePrefix (if configured)

In dev, $env/dynamic includes environment variables from .env. In prod, this behavior will depend on your adapter.

To get correct types, environment variables referenced in your code should be declared (for example in an .env file), even if they don't have a value until the app is deployed:

MY_FEATURE_FLAG=

You can override .env values from the command line like so:

MY_FEATURE_FLAG="enabled" npm run dev

For example, given the following runtime environment:

ENVIRONMENT=production
PUBLIC_BASE_URL=http://site.com

With the default publicPrefix and privatePrefix:

import { import env
referenceenv } from '$env/dynamic/private';

var console: Consoleconsole.Console.log(...data: any[]): void
MDN Reference
log(import env
referenceenv.ENVIRONMENT); // => "production"
var console: Consoleconsole.Console.log(...data: any[]): void
MDN Reference
log(import env
referenceenv.PUBLIC_BASE_URL); // => undefined