Files
Job-Info/ModeTemplate/frontend/.svelte-kit/ambient.d.ts
T
aewing 05f8e2e3b6 Add ModeTemplate with Svelte 5 frontend and components
- Create reusable components: auth, api-client, shared-types
- ModeTemplate with Hono backend and SvelteKit frontend
- Auth store refactored to class-based Svelte 5 pattern
- SSR-safe hydrate() pattern for localStorage access
- Frontend builds successfully with Svelte 5 runes
2026-01-21 05:12:25 +00:00

176 lines
6.5 KiB
TypeScript

// 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 COLORTERM: string;
export const HISTCONTROL: string;
export const TERM_PROGRAM_VERSION: string;
export const NODE: string;
export const npm_config_local_prefix: string;
export const PWD: string;
export const LOGNAME: string;
export const XDG_SESSION_TYPE: string;
export const _: string;
export const VSCODE_GIT_ASKPASS_NODE: string;
export const MOTD_SHOWN: string;
export const HOME: string;
export const LANG: string;
export const npm_package_version: string;
export const SSL_CERT_DIR: string;
export const GIT_ASKPASS: string;
export const SSH_CONNECTION: string;
export const npm_lifecycle_script: string;
export const VSCODE_GIT_ASKPASS_EXTRA_ARGS: string;
export const VSCODE_PYTHON_AUTOACTIVATE_GUARD: string;
export const XDG_SESSION_CLASS: string;
export const TERM: string;
export const npm_package_name: string;
export const USER: string;
export const GIT_PAGER: string;
export const VSCODE_GIT_IPC_HANDLE: string;
export const npm_lifecycle_event: string;
export const SHLVL: string;
export const XDG_SESSION_ID: string;
export const npm_config_user_agent: string;
export const npm_execpath: string;
export const XDG_RUNTIME_DIR: string;
export const SSL_CERT_FILE: string;
export const SSH_CLIENT: string;
export const DEBUGINFOD_URLS: string;
export const npm_package_json: string;
export const BUN_INSTALL: string;
export const VSCODE_GIT_ASKPASS_MAIN: string;
export const BROWSER: string;
export const PATH: string;
export const DBUS_SESSION_BUS_ADDRESS: string;
export const MAIL: string;
export const npm_node_execpath: string;
export const OLDPWD: string;
export const TERM_PROGRAM: string;
export const VSCODE_IPC_HOOK_CLI: 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;
COLORTERM: string;
HISTCONTROL: string;
TERM_PROGRAM_VERSION: string;
NODE: string;
npm_config_local_prefix: string;
PWD: string;
LOGNAME: string;
XDG_SESSION_TYPE: string;
_: string;
VSCODE_GIT_ASKPASS_NODE: string;
MOTD_SHOWN: string;
HOME: string;
LANG: string;
npm_package_version: string;
SSL_CERT_DIR: string;
GIT_ASKPASS: string;
SSH_CONNECTION: string;
npm_lifecycle_script: string;
VSCODE_GIT_ASKPASS_EXTRA_ARGS: string;
VSCODE_PYTHON_AUTOACTIVATE_GUARD: string;
XDG_SESSION_CLASS: string;
TERM: string;
npm_package_name: string;
USER: string;
GIT_PAGER: string;
VSCODE_GIT_IPC_HANDLE: string;
npm_lifecycle_event: string;
SHLVL: string;
XDG_SESSION_ID: string;
npm_config_user_agent: string;
npm_execpath: string;
XDG_RUNTIME_DIR: string;
SSL_CERT_FILE: string;
SSH_CLIENT: string;
DEBUGINFOD_URLS: string;
npm_package_json: string;
BUN_INSTALL: string;
VSCODE_GIT_ASKPASS_MAIN: string;
BROWSER: string;
PATH: string;
DBUS_SESSION_BUS_ADDRESS: string;
MAIL: string;
npm_node_execpath: string;
OLDPWD: string;
TERM_PROGRAM: string;
VSCODE_IPC_HOOK_CLI: 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;
}
}