astro 5.16.5 → 6.0.0-alpha.1

package/dist/types/public/config.d.ts

@@ -2,7 +2,7 @@ import type { OutgoingHttpHeaders } from 'node:http';
 import type { RemotePattern } from '@astrojs/internal-helpers/remote';
 import type { RehypePlugins, RemarkPlugins, RemarkRehype, ShikiConfig, SyntaxHighlightConfigType } from '@astrojs/markdown-remark';
 import type { Config as SvgoConfig } from 'svgo';
-import type { BuiltinDriverName, BuiltinDriverOptions, Driver, Storage } from 'unstorage';
+import type { BuiltinDriverName, BuiltinDriverOptions, Storage } from 'unstorage';
 import type { UserConfig as OriginalViteUserConfig, SSROptions as ViteSSROptions } from 'vite';
 import type { AstroFontProvider, FontFamily } from '../../assets/fonts/types.js';
 import type { ImageFit, ImageLayout } from '../../assets/types.js';
@@ -137,11 +137,7 @@ interface TestSessionConfig extends CommonSessionConfig {
 export type SessionConfig<TDriver extends SessionDriverName> = [
     TDriver
 ] extends [never] ? CustomSessionConfig : TDriver extends keyof BuiltinDriverOptions ? BuiltinSessionConfig<TDriver> : TDriver extends 'test' ? TestSessionConfig : CustomSessionConfig;
-export type ResolvedSessionConfig<TDriver extends SessionDriverName> = SessionConfig<TDriver> & {
-    driverModule?: () => Promise<{
-        default: () => Driver;
-    }>;
-};
+export type ResolvedSessionConfig<TDriver extends SessionDriverName> = SessionConfig<TDriver>;
 export interface ViteUserConfig extends OriginalViteUserConfig {
     ssr?: ViteSSROptions;
 }
@@ -480,6 +476,52 @@ export interface AstroUserConfig<TLocales extends Locales = never, TSession exte
      * Using `'attribute'` is useful when you are manipulating the `class` attribute of elements and need to avoid conflicts between your own styling logic and Astro's application of styles.
      */
     scopedStyleStrategy?: 'where' | 'class' | 'attribute';
+    /**
+     *
+     * @name prerenderConflictBehavior
+     * @type {'error' | 'warn' | 'ignore'}
+     * @default `'warn'`
+     * @version 6.0
+     * @description
+     * Determines the default behavior when two routes generate the same prerendered URL:
+     * - `error`: fail the build and display an error, forcing you to resolve the conflict
+     * - `warn` (default): log a warning when conflicts occur, but build using the highest-priority route
+     * - `ignore`: silently build using the highest-priority route when conflicts occur
+     */
+    prerenderConflictBehavior?: 'error' | 'warn' | 'ignore';
+    /**
+     * @docs
+     * @name vite
+     * @typeraw {ViteUserConfig}
+     * @description
+     *
+     * Pass additional configuration options to Vite. Useful when Astro doesn't support some advanced configuration that you may need.
+     *
+     * View the full `vite` configuration object documentation on [vite.dev](https://vite.dev/config/).
+     *
+     * #### Examples
+     *
+     * ```js
+     * {
+     *   vite: {
+     *     ssr: {
+     *       // Example: Force a broken package to skip SSR processing, if needed
+     *       external: ['broken-npm-package'],
+     *     }
+     *   }
+     * }
+     * ```
+     *
+     * ```js
+     * {
+     *   vite: {
+     *     // Example: Add custom vite plugins directly to your Astro project
+     *     plugins: [myPlugin()],
+     *   }
+     * }
+     * ```
+     */
+    vite?: ViteUserConfig;
     /**
      * @docs
      * @name security
@@ -563,40 +605,319 @@ export interface AstroUserConfig<TLocales extends Locales = never, TSession exte
          * When not configured, `X-Forwarded-Host` headers are not trusted and will be ignored.
          */
         allowedDomains?: Partial<RemotePattern>[];
+        /**
+         * @docs
+         * @name security.csp
+         * @kind h4
+         * @type {boolean | object}
+         * @default `false`
+         * @version 6.0.0
+         * @description
+         *
+         * Enables support for [Content Security Policy (CSP)](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) to help minimize certain types of security threats by controlling which resources a document is allowed to load. This provides additional protection against [cross-site scripting (XSS)](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting) attacks.
+         *
+         * Enabling this feature adds additional security to Astro's handling of processed and bundled scripts and styles by default, and allows you to further configure these, and additional, content types.
+         *
+         * This feature comes with some limitations:
+         * - External scripts and external styles are not supported out of the box, but you can [provide your own hashes](https://v6.docs.astro.build/en/reference/configuration-reference/#hashes).
+         * - [Astro's view transitions](https://v6.docs.astro.build/en/guides/view-transitions/) using the `<ClientRouter />` are not supported, but you can [consider migrating to the browser native View Transition API](https://events-3bg.pages.dev/jotter/astro-view-transitions/) instead if you are not using Astro's enhancements to the native View Transitions and Navigation APIs.
+         * - Shiki isn't currently supported. By design, Shiki functions using inline styles.
+         *
+         * :::note
+         * Due to the nature of the Vite dev server, this feature isn't supported while working in `dev` mode. Instead, you can test this in your Astro project using `build` and `preview`.
+         * :::
+         *
+         * When enabled, Astro will add a `<meta>` element inside the `<head>` element of each page.
+         * This element will have the `http-equiv="content-security-policy"` attribute, and the `content` attribute will provide values for the `script-src` and `style-src` [directives](https://v6.docs.astro.build/en/reference/configuration-reference/#securitycspdirectives) based on the script and styles used in the page.
+         *
+         * ```html
+         *
+         * <head>
+         *   <meta
+         *     http-equiv="content-security-policy"
+         *     content="
+         *     script-src 'self' 'sha256-somehash';
+         *     style-src 'self' 'sha256-somehash';
+         *     "
+         *   >
+         * </head>
+         * ```
+         *
+         * You can further customize the `<meta>` element by enabling this feature with a configuration object that includes additional options.
+         */
+        csp?: boolean | {
+            /**
+             * @name security.csp.algorithm
+             * @type {"SHA-256" | "SHA-384" | "SHA-512"}
+             * @default `'SHA-256'`
+             * @version 6.0.0
+             * @description
+             *
+             * The [hash function](https://developer.mozilla.org/en-US/docs/Glossary/Hash_function) to use when generating the hashes of the styles and scripts emitted by Astro.
+             *
+             * ```js title="astro.config.mjs"
+             * import { defineConfig } from 'astro/config';
+             *
+             * export default defineConfig({
+             *   security: {
+             *     csp: {
+             *      algorithm: 'SHA-512'
+             *     }
+             *   }
+             * });
+             * ```
+             */
+            algorithm?: CspAlgorithm;
+            /**
+             * @name security.csp.directives
+             * @type {string[]}
+             * @default `[]`
+             * @version 6.0.0
+             * @description
+             *
+             * A list of [CSP directives](https://content-security-policy.com/#directive) (beyond `script-src` and `style-src` which are included by default) that defines valid sources for specific content types. These directives are added to all pages.
+             *
+             * ```js title="astro.config.mjs"
+             * import { defineConfig } from 'astro/config';
+             *
+             * export default defineConfig({
+             *   security: {
+             *     csp: {
+             *       directives: [
+             *         "default-src 'self'",
+             *         "img-src 'self' https://images.cdn.example.com"
+             *       ]
+             *     }
+             *   }
+             * });
+             * ```
+             * After the build, the `<meta>` element will add your directives into the `content` value alongside Astro's default directives:
+             *
+             * ```html
+             * <meta
+             *   http-equiv="content-security-policy"
+             *   content="
+             *     default-src 'self';
+             *     img-src 'self' 'https://images.cdn.example.com';
+             *     script-src 'self' 'sha256-somehash';
+             *     style-src 'self' 'sha256-somehash';
+             *   "
+             * >
+             * ```
+             */
+            directives?: CspDirective[];
+            /**
+             * @name security.csp.styleDirective
+             * @type {{ hashes?: CspHash[], resources?: string[] }}
+             * @default `undefined`
+             * @version 6.0.0
+             * @description
+             *
+             * A configuration object that allows you to override the default sources for the `style-src` directive with the [`resources`](https://v6.docs.astro.build/en/reference/configuration-reference/#resources) property, or to provide additional [hashes]((https://v6.docs.astro.build/en/reference/configuration-reference#hashes) to be rendered.					 */
+            styleDirective?: {
+                /**
+                 * @name security.csp.styleDirective.hashes
+                 * @type {CspHash[]}
+                 * @default `[]`
+                 * @version 6.0.0
+                 * @description
+                 *
+                 * A list of additional hashes to be rendered.
+                 *
+                 * You must provide hashes that start with `sha384-`, `sha512-` or `sha256-`. Other values will cause a validation error. These hashes are added to all pages.
+                 *
+                 * ```js title="astro.config.mjs"
+                 * import { defineConfig } from 'astro/config';
+                 *
+                 * export default defineConfig({
+                 *   security: {
+                 *     csp: {
+                 *       styleDirective: {
+                 *         hashes: [
+                 *           "sha384-styleHash",
+                 *           "sha512-styleHash",
+                 *           "sha256-styleHash"
+                 *         ]
+                 *       }
+                 *     }
+                 *   }
+                 * });
+                 * ```
+                 *
+                 * After the build, the `<meta>` element will include your additional hashes in the `style-src` directives:
+                 *
+                 * ```html
+                 * <meta
+                 *   http-equiv="content-security-policy"
+                 *   content="
+                 *     style-src 'self' 'sha384-styleHash' 'sha512-styleHash' 'sha256-styleHash' 'sha256-generatedByAstro';
+                 *   "
+                 * >
+                 * ```
+                 */
+                hashes?: CspHash[];
+                /**
+                 * @name security.csp.styleDirective.resources
+                 * @type {string[]}
+                 * @default `[]`
+                 * @version 6.0.0
+                 * @description
+                 *
+                 * A list of valid sources for `style-src` directives to override Astro's default sources. This will not include `'self'` by default, and must be included in this list if you wish to keep it. These resources are added to all pages.
+                 *
+                 * ```js title="astro.config.mjs"
+                 * import { defineConfig } from 'astro/config';
+                 *
+                 * export default defineConfig({
+                 *   security: {
+                 *     csp: {
+                 *       styleDirective: {
+                 *         resources: [
+                 *           "'self'",
+                 *           "https://styles.cdn.example.com"
+                 *         ]
+                 *       }
+                 *     }
+                 *   }
+                 * });
+                 * ```
+                 *
+                 * After the build, the `<meta>` element will instead apply your sources to the `style-src` directives:
+                 *
+                 * ```html
+                 * <head>
+                 *   <meta
+                 *     http-equiv="content-security-policy"
+                 *     content="
+                 *      style-src 'self' https://styles.cdn.example.com 'sha256-somehash';
+                 *     "
+                 *   >
+                 * </head>
+                 * ```
+                 *
+                 * When resources are inserted multiple times or from multiple sources (e.g. defined in your `csp` config and added using [the CSP runtime API](/en/reference/api-reference/#csp)), Astro will merge and deduplicate all resources to create your `<meta>` element.
+                 */
+                resources?: string[];
+            };
+            /**
+             * @name security.csp.scriptDirective
+             * @type {{ hashes?: CspHash[], resources?: string[], strictDynamic?: boolean }}
+             * @default `undefined`
+             * @version 6.0.0
+             * @description
+             *
+             * A configuration object that allows you to override the default sources for the `script-src` directive with the [`resources`](https://v6.docs.astro.build/en/reference/configuration-reference/#resources) property, or to provide additional [hashes]((https://v6.docs.astro.build/en/reference/configuration-reference#hashes) to be rendered.
+             */
+            scriptDirective?: {
+                /**
+                 * @name security.csp.scriptDirective.hashes
+                 * @type {CspHash[]}
+                 * @default `[]`
+                 * @version 6.0.0
+                 * @description
+                 *
+                 * A list of additional hashes to be rendered.
+                 *
+                 * You must provide hashes that start with `sha384-`, `sha512-` or `sha256-`. Other values will cause a validation error. These hashes are added to all pages.
+                 *
+                 * ```js title="astro.config.mjs"
+                 * import { defineConfig } from 'astro/config';
+                 *
+                 * export default defineConfig({
+                 *   security: {
+                 *     csp: {
+                 *       scriptDirective: {
+                 *         hashes: [
+                 *           "sha384-scriptHash",
+                 *           "sha512-scriptHash",
+                 *           "sha256-scriptHash"
+                 *         ]
+                 *       }
+                 *     }
+                 *   }
+                 * });
+                 * ```
+                 *
+                 * After the build, the `<meta>` element will include your additional hashes in the `script-src` directives:
+                 *
+                 * ```html
+                 * <meta
+                 *   http-equiv="content-security-policy"
+                 *   content="
+                 *     script-src 'self' 'sha384-scriptHash' 'sha512-scriptHash' 'sha256-scriptHash' 'sha256-generatedByAstro';
+                 *   "
+                 * >
+                 * ```
+                 */
+                hashes?: CspHash[];
+                /**
+                 * @name security.csp.scriptDirective.resources
+                 * @type {string[]}
+                 * @default `[]`
+                 * @version 6.0.0
+                 * @description
+                 *
+                 * A list of valid sources for the `script-src` directives to override Astro's default sources. This will not include `'self'` by default, and must be included in this list if you wish to keep it. These resources are added to all pages.
+                 *
+                 * ```js title="astro.config.mjs"
+                 * import { defineConfig } from 'astro/config';
+                 *
+                 * export default defineConfig({
+                 *   security: {
+                 *     csp: {
+                 *       scriptDirective: {
+                 *         resources: [
+                 *           "'self'", "https://cdn.example.com"
+                 *         ]
+                 *       }
+                 *     }
+                 *   }
+                 * });
+                 * ```
+                 *
+                 * After the build, the `<meta>` element will instead apply your sources to the `script-src` directives:
+                 *
+                 * ```html
+                 * <head>
+                 *   <meta
+                 *     http-equiv="content-security-policy"
+                 *     content="
+                 *      script-src 'self' https://cdn.example.com 'sha256-somehash';
+                 *     "
+                 *   >
+                 * </head>
+                 * ```
+                 *
+                 * When resources are inserted multiple times or from multiple sources (e.g. defined in your `csp` config and added using [the CSP runtime API](/en/reference/api-reference/#csp)), Astro will merge and deduplicate all resources to create your `<meta>` element.
+                 */
+                resources?: string[];
+                /**
+                 * @name security.csp.scriptDirective.strictDynamic
+                 * @type {boolean}
+                 * @default `false`
+                 * @version 6.0.0
+                 * @description
+                 *
+                 * Enables [the `strict-dynamic` keyword](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP#the_strict-dynamic_keyword) to support the dynamic injection of scripts.
+                 *
+                 * ```js title="astro.config.mjs"
+                 * import { defineConfig } from 'astro/config';
+                 *
+                 * export default defineConfig({
+                 *   security: {
+                 *     csp: {
+                 *       scriptDirective: {
+                 *         strictDynamic: true
+                 *       }
+                 *     }
+                 *   }
+                 * });
+                 * ```
+                 */
+                strictDynamic?: boolean;
+            };
+        };
     };
-    /**
-     * @docs
-     * @name vite
-     * @typeraw {ViteUserConfig}
-     * @description
-     *
-     * Pass additional configuration options to Vite. Useful when Astro doesn't support some advanced configuration that you may need.
-     *
-     * View the full `vite` configuration object documentation on [vite.dev](https://vite.dev/config/).
-     *
-     * #### Examples
-     *
-     * ```js
-     * {
-     *   vite: {
-     *     ssr: {
-     *       // Example: Force a broken package to skip SSR processing, if needed
-     *       external: ['broken-npm-package'],
-     *     }
-     *   }
-     * }
-     * ```
-     *
-     * ```js
-     * {
-     *   vite: {
-     *     // Example: Add custom vite plugins directly to your Astro project
-     *     plugins: [myPlugin()],
-     *   }
-     * }
-     * ```
-     */
-    vite?: ViteUserConfig;
     /**
      * @docs
      * @kind heading
@@ -1705,14 +2026,14 @@ export interface AstroUserConfig<TLocales extends Locales = never, TSession exte
              * @name i18n.routing.redirectToDefaultLocale
              * @kind h4
              * @type {boolean}
-             * @default `true`
+             * @default `false`
              * @version 4.2.0
              * @description
              *
              * Configures whether or not the home URL (`/`) generated by `src/pages/index.astro`
              * will redirect to `/[defaultLocale]` when `prefixDefaultLocale: true` is set.
              *
-             * Set `redirectToDefaultLocale: false` to disable this automatic redirection at the root of your site:
+             * Set `redirectToDefaultLocale: true` to enable this automatic redirection at the root of your site:
              * ```js
              * // astro.config.mjs
              * export default defineConfig({
@@ -1721,7 +2042,7 @@ export interface AstroUserConfig<TLocales extends Locales = never, TSession exte
              * 		locales: ["en", "fr"],
              *     routing: {
              *       prefixDefaultLocale: true,
-             *       redirectToDefaultLocale: false
+             *       redirectToDefaultLocale: true
              *     }
              *   }
              * })
@@ -1922,48 +2243,7 @@ export interface AstroUserConfig<TLocales extends Locales = never, TSession exte
      * These flags allow you to opt in to some deprecated or otherwise outdated behavior of Astro
      * in the latest version, so that you can continue to upgrade and take advantage of new Astro releases.
      */
-    legacy?: {
-        /**
-         *
-         * @name legacy.collections
-         * @type {boolean}
-         * @default `false`
-         * @version 5.0.0
-         * @description
-         * Enable legacy behavior for content collections.
-         *
-         * ```js
-         * // astro.config.mjs
-         * import { defineConfig } from 'astro/config';
-         * export default defineConfig({
-         *   legacy: {
-         *     collections: true
-         *   }
-         * });
-         * ```
-         *
-         * If enabled, `data` and `content` collections (only) are handled using the legacy content collections implementation. Collections with a `loader` (only) will continue to use the Content Layer API instead. Both kinds of collections may exist in the same project, each using their respective implementations.
-         *
-         *  The following limitations continue to exist:
-         *
-         * - Any legacy (`type: 'content'` or `type: 'data'`) collections must continue to be located in the `src/content/` directory.
-         * - These legacy collections will not be transformed to implicitly use the `glob()` loader, and will instead be handled by legacy code.
-         * - Collections using the Content Layer API (with a `loader` defined) are forbidden in `src/content/`, but may exist anywhere else in your project.
-         *
-         * When you are ready to remove this flag and migrate to the new Content Layer API for your legacy collections, you must define a collection for any directories in `src/content/` that you want to continue to use as a collection. It is sufficient to declare an empty collection, and Astro will implicitly generate an appropriate definition for your legacy collections:
-         *
-         * ```js
-         * // src/content.config.ts
-         * import { defineCollection, z } from 'astro:content';
-         *
-         * const blog = defineCollection({ })
-         *
-         * export const collections = { blog };
-         * ```
-         *
-         */
-        collections?: boolean;
-    };
+    legacy?: Record<string, never>;
     /**
      *
      * @kind heading
@@ -2008,17 +2288,6 @@ export interface AstroUserConfig<TLocales extends Locales = never, TSession exte
          * See the [Prefetch Guide](https://docs.astro.build/en/guides/prefetch/) for more `prefetch` options and usage.
          */
         clientPrerender?: boolean;
-        /**
-         *
-         * @name experimental.failOnPrerenderConflict
-         * @type {boolean}
-         * @default `false`
-         * @version 5.x
-         * @description
-         * When two routes generate the same prerendered URL, fail the build instead of skipping one.
-         * If disabled (default), a warning is logged when conflicts occur and the highest-priority route wins.
-         */
-        failOnPrerenderConflict?: boolean;
         /**
          *
          * @name experimental.contentIntellisense
@@ -2060,326 +2329,6 @@ export interface AstroUserConfig<TLocales extends Locales = never, TSession exte
          * see the [Fonts RFC](https://github.com/withastro/roadmap/pull/1039).
          */
         fonts?: FontFamily[];
-        /**
-         * @name experimental.headingIdCompat
-         * @type {boolean}
-         * @default `false`
-         * @version 5.5.x
-         * @description
-         *
-         * Enables full compatibility of Markdown headings IDs with common platforms such as GitHub and npm.
-         *
-         * When enabled, IDs for headings ending with non-alphanumeric characters, e.g. `<Picture />`, will
-         * include a trailing `-`, matching standard behavior in other Markdown tooling.
-         */
-        headingIdCompat?: boolean;
-        /**
-         * @name experimental.csp
-         * @type {boolean | object}
-         * @default `false`
-         * @version 5.9.0
-         * @description
-         *
-         * Enables built-in support for Content Security Policy (CSP). For more information,
-         * refer to the [experimental CSP documentation](https://docs.astro.build/en/reference/experimental-flags/csp/)
-         *
-         */
-        csp?: boolean | {
-            /**
-             * @name experimental.csp.algorithm
-             * @type {"SHA-256" | "SHA-384" | "SHA-512"}
-             * @default `'SHA-256'`
-             * @version 5.9.0
-             * @description
-             *
-             * The [hash function](https://developer.mozilla.org/en-US/docs/Glossary/Hash_function) to use to generate the hashes of the styles and scripts emitted by Astro.
-             *
-             * ```js
-             * import { defineConfig } from 'astro/config';
-             *
-             * export default defineConfig({
-             *   experimental: {
-             *     csp: {
-             *       algorithm: 'SHA-512'
-             *     }
-             *   }
-             * });
-             * ```
-             */
-            algorithm?: CspAlgorithm;
-            /**
-             * @name experimental.csp.styleDirective
-             * @type {{ hashes?: CspHash[], resources?: string[] }}
-             * @default `undefined`
-             * @version 5.9.0
-             * @description
-             *
-             * A configuration object that allows you to override the default sources for the `style-src` directive
-             * with the `resources` property, or to provide additional `hashes` to be rendered.
-             *
-             * These properties are added to all pages and completely override Astro's default resources, not add to them.
-             * Therefore, you must explicitly specify any default values that you want to be included.
-             */
-            styleDirective?: {
-                /**
-                 * @name experimental.csp.styleDirective.hashes
-                 * @type {CspHash[]}
-                 * @default `[]`
-                 * @version 5.9.0
-                 * @description
-                 *
-                 * A list of additional hashes added to the `style-src` directive.
-                 *
-                 * If you have external styles that aren't generated by Astro, this configuration option allows you to provide additional hashes to be rendered.
-                 *
-                 * You must provide hashes that start with `sha384-`, `sha512-` or `sha256-`. Other values will cause a validation error. These hashes are added to all pages.
-                 *
-                 * ```js
-                 * import { defineConfig } from 'astro/config';
-                 *
-                 * export default defineConfig({
-                 *   experimental: {
-                 *     csp: {
-                 *       styleDirective: {
-                 *         hashes: [
-                 *           "sha384-styleHash",
-                 *           "sha512-styleHash",
-                 *           "sha256-styleHash"
-                 *         ]
-                 *       }
-                 *     }
-                 *   }
-                 * });
-                 * ```
-                 */
-                hashes?: CspHash[];
-                /**
-                 * @name experimental.csp.styleDirective.resources
-                 * @type {string[]}
-                 * @default `[]`
-                 * @version 5.9.0
-                 * @description
-                 *
-                 * A list of resources applied to the `style-src` directive. These resources are added to all pages and will override Astro's defaults.
-                 *
-                 * ```js
-                 * import { defineConfig } from 'astro/config';
-                 *
-                 * export default defineConfig({
-                 *   experimental: {
-                 *     csp: {
-                 *       styleDirective: {
-                 *         resources: [
-                 *           "'self'",
-                 *           "https://styles.cdn.example.com"
-                 *         ]
-                 *       }
-                 *     }
-                 *   }
-                 * });
-                 * ```
-                 */
-                resources?: string[];
-            };
-            /**
-             * @name experimental.csp.scriptDirective
-             * @type {{ hashes?: CspHash[], resources?: string[], strictDynamic?: boolean }}
-             * @default `undefined`
-             * @version 5.9.0
-             * @description
-             *
-             * A configuration object that allows you to override the default sources for the `script-src` directive
-             * with the `resources` property, or to provide additional `hashes` to be rendered.
-             *
-             * These properties are added to all pages and completely override Astro's default resources, not add to them.
-             * Therefore, you must explicitly specify any default values that you want to be included.
-             *
-             */
-            scriptDirective?: {
-                /**
-                 * @name experimental.csp.scriptDirective.hashes
-                 * @type {CspHash[]}
-                 * @default `[]`
-                 * @version 5.9.0
-                 * @description
-                 *
-                 * A list of additional hashes added to the `script-src` directive.
-                 *
-                 * If you have external scripts that aren't generated by Astro, or inline scripts, this configuration option allows you to provide additional hashes to be rendered.
-                 *
-                 * You must provide hashes that start with `sha384-`, `sha512-` or `sha256-`. Other values will cause a validation error. These hashes are added to all pages.
-                 *
-                 * ```js
-                 * import { defineConfig } from 'astro/config';
-                 *
-                 * export default defineConfig({
-                 *   experimental: {
-                 *     csp: {
-                 *       scriptDirective: {
-                 *         hashes: [
-                 *           "sha384-scriptHash",
-                 *           "sha512-scriptHash",
-                 *           "sha256-scriptHash"
-                 *         ]
-                 *       }
-                 *     }
-                 *   }
-                 * });
-                 * ```
-                 */
-                hashes?: CspHash[];
-                /**
-                 * @name experimental.csp.scriptDirective.resources
-                 * @type {string[]}
-                 * @default `[]`
-                 * @version 5.9.0
-                 * @description
-                 *
-                 * A list of resources applied to the `script-src` directive. These resources are added to all pages and will override Astro's defaults.
-                 *
-                 * ```js
-                 * import { defineConfig } from 'astro/config';
-                 *
-                 * export default defineConfig({
-                 *   experimental: {
-                 *     csp: {
-                 *       scriptDirective: {
-                 *         resources: [
-                 *           "'self'",
-                 *           "https://cdn.example.com"
-                 *         ]
-                 *       }
-                 *     }
-                 *   }
-                 * });
-                 * ```
-                 *
-                 */
-                resources?: string[];
-                /**
-                 * @name experimental.csp.scriptDirective.strictDynamic
-                 * @type {boolean}
-                 * @default `false`
-                 * @version 5.9.0
-                 * @description
-                 *
-                 * Enables the keyword `strict-dynamic` to support the dynamic injection of scripts.
-                 *
-                 * ```js
-                 * import { defineConfig } from 'astro/config';
-                 *
-                 * export default defineConfig({
-                 *   experimental: {
-                 *     csp: {
-                 *       scriptDirective: {
-                 *         strictDynamic: true
-                 *       }
-                 *     }
-                 *   }
-                 * });
-                 * ```
-                 */
-                strictDynamic?: boolean;
-            };
-            /**
-             * @name experimental.csp.directives
-             * @type {string[]}
-             * @default `[]`
-             * @version 5.9.0
-             * @description
-             *
-             * An array of additional directives to add the content of the `Content-Security-Policy` `<meta>` element.
-             *
-             * Use this configuration to add other directive definitions such as `default-src`, `image-src`, etc.
-             *
-             * ##### Example
-             *
-             * You can define a directive to fetch images only from a CDN `cdn.example.com`.
-             *
-             * ```js
-             * export default defineConfig({
-             * 	experimental: {
-             * 		csp: {
-             * 			directives: [
-             * 				"image-src 'https://cdn.example.com"
-             * 			]
-             * 		}
-             * 	}
-             * })
-             * ```
-             *
-             */
-            directives?: CspDirective[];
-        };
-        /**
-         * @name experimental.preserveScriptOrder
-         * @type {boolean}
-         * @default `false`
-         * @version 5.5
-         * @description
-         *
-         * When enabled, `<script>` and `<style>` tags are rendered in the same order as they are defined.
-         *
-         * ## Example
-         *
-         * Consider the following component:
-         *
-         * ```html
-         * <p>I am a component</p>
-         * <style>
-         *   body {
-         *     background: red;
-         *   }
-         * </style>
-         * <style>
-         *   body {
-         *     background: yellow;
-         *   }
-         * </style>
-         * ```
-         *
-         * By default, it will generate a CSS style where `red` will be applied:
-         *
-         * ```css
-         * body {background:#ff0} body {background:red}
-         * ```
-         *
-         * When this new option is set to `true`, the generated CSS style will apply `yellow`:
-         *
-         * ```css
-         * body {background:red} body {background:#ff0}
-         * ```
-         *
-         */
-        preserveScriptOrder?: boolean;
-        /**
-         * @name experimental.liveContentCollections
-         * @type {boolean}
-         * @default `false`
-         * @version 5.10
-         * @description
-         * Enables the use of live content collections.
-         *
-         */
-        liveContentCollections?: boolean;
-        /**
-         * @name experimental.staticImportMetaEnv
-         * @type {boolean}
-         * @default `false`
-         * @version 5.13
-         * @description
-         *
-         * Disables replacement of `import.meta.env` values with `process.env` calls and their coercion
-         *
-         * Currently, non-public `import.meta.env` environment variables are replaced by a reference to `process.env`. Additionally, Astro may also convert the value type of your environment variables used through `import.meta.env`, which can prevent access to some values such as the strings `"true"` (which is converted to a boolean value), and `"1"` (which is converted to a number).
-         *
-         * The `experimental.staticImportMetaEnv` flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any `import.meta.env` environment variables with a `process.env` call, nor will it coerce values.
-         *
-         * This flag aligns `import.meta.env`'s behavior in Astro with [Vite](https://vite.dev/guide/env-and-mode.html#env-variables).
-         *
-         * See the [experimental static `import.meta.env` docs](https://docs.astro.build/en/reference/experimental-flags/static-import-meta-env/) for more information.
-         */
-        staticImportMetaEnv?: boolean;
         /**
          * @name experimental.chromeDevtoolsWorkspace
          * @type {boolean}