@sveltejs/kit 2.62.0 → 3.0.0-next.0

package/src/types/synthetic/$env+dynamic+private.md

@@ -1,43 +0,0 @@
-This module provides access to environment variables set _dynamically_ at runtime and that are limited to _private_ access.
-
-|         | Runtime                                                                    | Build time                                                               |
-| ------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
-| Private | [`$env/dynamic/private`](https://svelte.dev/docs/kit/$env-dynamic-private) | [`$env/static/private`](https://svelte.dev/docs/kit/$env-static-private) |
-| Public  | [`$env/dynamic/public`](https://svelte.dev/docs/kit/$env-dynamic-public)   | [`$env/static/public`](https://svelte.dev/docs/kit/$env-static-public)   |
-
-Dynamic environment variables are 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`.
-
-**_Private_ access:**
-
-- This module cannot be imported into client-side code
-- This module 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)
-
-> [!NOTE] In `dev`, `$env/dynamic` includes environment variables from `.env`. In `prod`, this behavior will depend on your adapter.
-
-> [!NOTE] 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:
->
-> ```env
-> MY_FEATURE_FLAG=
-> ```
->
-> You can override `.env` values from the command line like so:
->
-> ```sh
-> MY_FEATURE_FLAG="enabled" npm run dev
-> ```
-
-For example, given the following runtime environment:
-
-```env
-ENVIRONMENT=production
-PUBLIC_BASE_URL=http://site.com
-```
-
-With the default `publicPrefix` and `privatePrefix`:
-
-```ts
-import { env } from '$env/dynamic/private';
-
-console.log(env.ENVIRONMENT); // => "production"
-console.log(env.PUBLIC_BASE_URL); // => undefined
-```

package/src/types/synthetic/$env+dynamic+public.md

@@ -1,46 +0,0 @@
-This module provides access to environment variables set _dynamically_ at runtime and that are _publicly_ accessible.
-
-|         | Runtime                                                                    | Build time                                                               |
-| ------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
-| Private | [`$env/dynamic/private`](https://svelte.dev/docs/kit/$env-dynamic-private) | [`$env/static/private`](https://svelte.dev/docs/kit/$env-static-private) |
-| Public  | [`$env/dynamic/public`](https://svelte.dev/docs/kit/$env-dynamic-public)   | [`$env/static/public`](https://svelte.dev/docs/kit/$env-static-public)   |
-
-Dynamic environment variables are 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`.
-
-**_Public_ access:**
-
-- This module _can_ be imported into client-side code
-- **Only** variables that begin with [`config.kit.env.publicPrefix`](https://svelte.dev/docs/kit/configuration#env) (which defaults to `PUBLIC_`) are included
-
-> [!NOTE] In `dev`, `$env/dynamic` includes environment variables from `.env`. In `prod`, this behavior will depend on your adapter.
-
-> [!NOTE] 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:
->
-> ```env
-> MY_FEATURE_FLAG=
-> ```
->
-> You can override `.env` values from the command line like so:
->
-> ```sh
-> MY_FEATURE_FLAG="enabled" npm run dev
-> ```
-
-For example, given the following runtime environment:
-
-```env
-ENVIRONMENT=production
-PUBLIC_BASE_URL=http://example.com
-```
-
-With the default `publicPrefix` and `privatePrefix`:
-
-```ts
-import { env } from '$env/dynamic/public';
-console.log(env.ENVIRONMENT); // => undefined, not public
-console.log(env.PUBLIC_BASE_URL); // => "http://example.com"
-```
-
-```
-
-```

package/src/types/synthetic/$env+static+private.md

@@ -1,31 +0,0 @@
-This module provides access to environment variables that are injected _statically_ into your bundle at build time and are limited to _private_ access.
-
-|         | Runtime                                                                    | Build time                                                               |
-| ------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
-| Private | [`$env/dynamic/private`](https://svelte.dev/docs/kit/$env-dynamic-private) | [`$env/static/private`](https://svelte.dev/docs/kit/$env-static-private) |
-| Public  | [`$env/dynamic/public`](https://svelte.dev/docs/kit/$env-dynamic-public)   | [`$env/static/public`](https://svelte.dev/docs/kit/$env-static-public)   |
-
-Static environment variables are [loaded by Vite](https://vitejs.dev/guide/env-and-mode.html#env-files) from `.env` files and `process.env` at build time and then statically injected into your bundle at build time, enabling optimisations like dead code elimination.
-
-**_Private_ access:**
-
-- 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)
-
-For example, given the following build time environment:
-
-```env
-ENVIRONMENT=production
-PUBLIC_BASE_URL=http://site.com
-```
-
-With the default `publicPrefix` and `privatePrefix`:
-
-```ts
-import { ENVIRONMENT, PUBLIC_BASE_URL } from '$env/static/private';
-
-console.log(ENVIRONMENT); // => "production"
-console.log(PUBLIC_BASE_URL); // => throws error during build
-```
-
-The above values will be the same _even if_ different values for `ENVIRONMENT` or `PUBLIC_BASE_URL` are set at runtime, as they are statically replaced in your code with their build time values.

package/src/types/synthetic/$env+static+public.md

@@ -1,31 +0,0 @@
-This module provides access to environment variables that are injected _statically_ into your bundle at build time and are _publicly_ accessible.
-
-|         | Runtime                                                                    | Build time                                                               |
-| ------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
-| Private | [`$env/dynamic/private`](https://svelte.dev/docs/kit/$env-dynamic-private) | [`$env/static/private`](https://svelte.dev/docs/kit/$env-static-private) |
-| Public  | [`$env/dynamic/public`](https://svelte.dev/docs/kit/$env-dynamic-public)   | [`$env/static/public`](https://svelte.dev/docs/kit/$env-static-public)   |
-
-Static environment variables are [loaded by Vite](https://vitejs.dev/guide/env-and-mode.html#env-files) from `.env` files and `process.env` at build time and then statically injected into your bundle at build time, enabling optimisations like dead code elimination.
-
-**_Public_ access:**
-
-- This module _can_ be imported into client-side code
-- **Only** variables that begin with [`config.kit.env.publicPrefix`](https://svelte.dev/docs/kit/configuration#env) (which defaults to `PUBLIC_`) are included
-
-For example, given the following build time environment:
-
-```env
-ENVIRONMENT=production
-PUBLIC_BASE_URL=http://site.com
-```
-
-With the default `publicPrefix` and `privatePrefix`:
-
-```ts
-import { ENVIRONMENT, PUBLIC_BASE_URL } from '$env/static/public';
-
-console.log(ENVIRONMENT); // => throws error during build
-console.log(PUBLIC_BASE_URL); // => "http://site.com"
-```
-
-The above values will be the same _even if_ different values for `ENVIRONMENT` or `PUBLIC_BASE_URL` are set at runtime, as they are statically replaced in your code with their build time values.

package/src/utils/env.js

@@ -1,13 +0,0 @@
-/**
- * @param {Record<string, string>} env
- * @param {string} allowed
- * @param {string} disallowed
- * @returns {Record<string, string>}
- */
-export function filter_env(env, allowed, disallowed) {
-	return Object.fromEntries(
-		Object.entries(env).filter(
-			([k]) => k.startsWith(allowed) && (disallowed === '' || !k.startsWith(disallowed))
-		)
-	);
-}

package/src/utils/promise.js

@@ -1,29 +0,0 @@
-/** @see https://github.com/microsoft/TypeScript/blob/904e7dd97dc8da1352c8e05d70829dff17c73214/src/lib/es2024.promise.d.ts */
-
-/**
- * @template T
- * @typedef {{
- *   promise: Promise<T>;
- *   resolve: (value: T | PromiseLike<T>) => void;
- *   reject: (reason?: any) => void;
- * }} PromiseWithResolvers<T>
- */
-
-/**
- * TODO: Whenever Node >21 is minimum supported version, we can use `Promise.withResolvers` to avoid this ceremony
- *
- * @template T
- * @returns {PromiseWithResolvers<T>}
- */
-export function with_resolvers() {
-	let resolve;
-	let reject;
-
-	const promise = new Promise((res, rej) => {
-		resolve = res;
-		reject = rej;
-	});
-
-	// @ts-expect-error `resolve` and `reject` are assigned!
-	return { promise, resolve, reject };
-}