File size: 7,221 Bytes
04ec17f |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 |
// this file is generated — do not edit it
/// <reference types="@sveltejs/kit" />
/**
* Environment variables [loaded by Vite](https://vitejs.dev/guide/env-and-mode.html#env-files) from `.env` files and `process.env`. Like [`$env/dynamic/private`](https://svelte.dev/docs/kit/$env-dynamic-private), this module cannot be imported into client-side code. This module only includes variables that _do not_ begin with [`config.kit.env.publicPrefix`](https://svelte.dev/docs/kit/configuration#env) _and do_ start with [`config.kit.env.privatePrefix`](https://svelte.dev/docs/kit/configuration#env) (if configured).
*
* _Unlike_ [`$env/dynamic/private`](https://svelte.dev/docs/kit/$env-dynamic-private), the values exported from this module are statically injected into your bundle at build time, enabling optimisations like dead code elimination.
*
* ```ts
* import { API_KEY } from '$env/static/private';
* ```
*
* Note that all 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:
*
* ```sh
* MY_FEATURE_FLAG="enabled" npm run dev
* ```
*/
declare module '$env/static/private' {
export const SHELL: string;
export const npm_command: string;
export const npm_config_userconfig: string;
export const npm_config_cache: string;
export const HISTCONTROL: string;
export const WSL2_GUI_APPS_ENABLED: string;
export const WSL_DISTRO_NAME: string;
export const TERMINAL_EMULATOR: string;
export const HOSTNAME: string;
export const HISTSIZE: string;
export const NODE: string;
export const TERM_SESSION_ID: string;
export const COLOR: string;
export const npm_config_local_prefix: string;
export const npm_config_globalconfig: string;
export const GPG_TTY: string;
export const EDITOR: string;
export const NAME: string;
export const PWD: string;
export const LOGNAME: string;
export const npm_config_init_module: string;
export const _: string;
export const HOME: string;
export const LANG: string;
export const WSL_INTEROP: string;
export const LS_COLORS: string;
export const npm_package_version: string;
export const WAYLAND_DISPLAY: string;
export const INIT_CWD: string;
export const npm_lifecycle_script: string;
export const npm_config_npm_version: string;
export const TERM: string;
export const npm_package_name: string;
export const npm_config_prefix: string;
export const LESSOPEN: string;
export const USER: string;
export const DISPLAY: string;
export const npm_lifecycle_event: string;
export const SHLVL: string;
export const npm_config_user_agent: string;
export const npm_execpath: string;
export const XDG_RUNTIME_DIR: string;
export const DEBUGINFOD_URLS: string;
export const npm_package_json: string;
export const WSLENV: string;
export const DEBUGINFOD_IMA_CERT_PATH: string;
export const npm_config_noproxy: string;
export const PATH: string;
export const npm_config_node_gyp: string;
export const DBUS_SESSION_BUS_ADDRESS: string;
export const npm_config_python: string;
export const npm_config_global_prefix: string;
export const npm_config_update_notifier: string;
export const MAIL: string;
export const HOSTTYPE: string;
export const PULSE_SERVER: string;
export const npm_node_execpath: string;
export const OLDPWD: string;
export const NODE_ENV: string;
}
/**
* Similar to [`$env/static/private`](https://svelte.dev/docs/kit/$env-static-private), except that it only includes environment variables that begin with [`config.kit.env.publicPrefix`](https://svelte.dev/docs/kit/configuration#env) (which defaults to `PUBLIC_`), and can therefore safely be exposed to client-side code.
*
* Values are replaced statically at build time.
*
* ```ts
* import { PUBLIC_BASE_URL } from '$env/static/public';
* ```
*/
declare module '$env/static/public' {
}
/**
* This module provides access to runtime environment variables, as defined by the platform you're running on. For example if you're using [`adapter-node`](https://github.com/sveltejs/kit/tree/main/packages/adapter-node) (or running [`vite preview`](https://svelte.dev/docs/kit/cli)), this is equivalent to `process.env`. This module only includes variables that _do not_ begin with [`config.kit.env.publicPrefix`](https://svelte.dev/docs/kit/configuration#env) _and do_ start with [`config.kit.env.privatePrefix`](https://svelte.dev/docs/kit/configuration#env) (if configured).
*
* This module cannot be imported into client-side code.
*
* ```ts
* import { env } from '$env/dynamic/private';
* console.log(env.DEPLOYMENT_SPECIFIC_VARIABLE);
* ```
*
* > [!NOTE] In `dev`, `$env/dynamic` always includes environment variables from `.env`. In `prod`, this behavior will depend on your adapter.
*/
declare module '$env/dynamic/private' {
export const env: {
SHELL: string;
npm_command: string;
npm_config_userconfig: string;
npm_config_cache: string;
HISTCONTROL: string;
WSL2_GUI_APPS_ENABLED: string;
WSL_DISTRO_NAME: string;
TERMINAL_EMULATOR: string;
HOSTNAME: string;
HISTSIZE: string;
NODE: string;
TERM_SESSION_ID: string;
COLOR: string;
npm_config_local_prefix: string;
npm_config_globalconfig: string;
GPG_TTY: string;
EDITOR: string;
NAME: string;
PWD: string;
LOGNAME: string;
npm_config_init_module: string;
_: string;
HOME: string;
LANG: string;
WSL_INTEROP: string;
LS_COLORS: string;
npm_package_version: string;
WAYLAND_DISPLAY: string;
INIT_CWD: string;
npm_lifecycle_script: string;
npm_config_npm_version: string;
TERM: string;
npm_package_name: string;
npm_config_prefix: string;
LESSOPEN: string;
USER: string;
DISPLAY: string;
npm_lifecycle_event: string;
SHLVL: string;
npm_config_user_agent: string;
npm_execpath: string;
XDG_RUNTIME_DIR: string;
DEBUGINFOD_URLS: string;
npm_package_json: string;
WSLENV: string;
DEBUGINFOD_IMA_CERT_PATH: string;
npm_config_noproxy: string;
PATH: string;
npm_config_node_gyp: string;
DBUS_SESSION_BUS_ADDRESS: string;
npm_config_python: string;
npm_config_global_prefix: string;
npm_config_update_notifier: string;
MAIL: string;
HOSTTYPE: string;
PULSE_SERVER: string;
npm_node_execpath: string;
OLDPWD: string;
NODE_ENV: string;
[key: `PUBLIC_${string}`]: undefined;
[key: `${string}`]: string | undefined;
}
}
/**
* Similar to [`$env/dynamic/private`](https://svelte.dev/docs/kit/$env-dynamic-private), but only includes variables that begin with [`config.kit.env.publicPrefix`](https://svelte.dev/docs/kit/configuration#env) (which defaults to `PUBLIC_`), and can therefore safely be exposed to client-side code.
*
* Note that public dynamic environment variables must all be sent from the server to the client, causing larger network requests — when possible, use `$env/static/public` instead.
*
* ```ts
* import { env } from '$env/dynamic/public';
* console.log(env.PUBLIC_DEPLOYMENT_SPECIFIC_VARIABLE);
* ```
*/
declare module '$env/dynamic/public' {
export const env: {
[key: `PUBLIC_${string}`]: string | undefined;
}
}
|