Repository: withastro/astro
File: packages/astro/src/types/public/config.ts (TypeScript)

Code before:
		 *
		 * ```js
		 * // astro.config.mjs
		 * import { defineConfig, envField } from "astro/config"
		 *
		 * export default defineConfig({
		 *   env: {
		 *     schema: {
		 *       // ...
		 *     },
		 *     validateSecrets: true
		 *   }
		 * })
		 * ```
		 */
		validateSecrets?: boolean;
	};

	/**
	 *
	 * @name prerenderConflictBehavior
	 * @type {'warning' | 'error' | 'ignore'}
	 * @default `'warning'`
	 * @version 6.0
	 * @description
	 * When two routes generate the same prerendered URL, defines Astro's behavior:
	 * - Error: fail the build
	 * - Warning (default): logs a warning when conflicts occur and the highest-priority route wins
	 * - Ignore: silently picks the highest-priority route when conflicts occur
	 */
	prerenderConflictBehavior?: 'warning' | 'error' | 'ignore';

	/**
	 *
	 * @kind heading
	 * @name Legacy Flags
	 * @description
	 * To help some users migrate between versions of Astro, we occasionally introduce `legacy` flags.
	 * 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?: Record<string, never>; // Currently no legacy flags are available.

	/**
	 *
	 * @kind heading
	 * @name Experimental Flags
	 * @description
	 * Astro offers experimental flags to give users early access to new features.
	 * These flags are not guaranteed to be stable.
	 */

Review comment (suggestion):
```suggestion
	 * Determines the default behavior when two routes generate the same prerendered URL:
```

Code after:
		 */
		schema?: EnvSchema;

		/**
		 * @docs
		 * @name env.validateSecrets
		 * @type {boolean}
		 * @default `false`
		 * @version 5.0.0
		 * @description
		 *
		 * Whether or not to validate secrets on the server when starting the dev server or running a build.
		 *
		 * By default, only public variables are validated on the server when starting the dev server or a build, and private variables are validated at runtime only. If enabled, private variables will also be checked on start. This is useful in some continuous integration (CI) pipelines to make sure all your secrets are correctly set before deploying.
		 *
		 * ```js
		 * // astro.config.mjs
		 * import { defineConfig, envField } from "astro/config"
		 *
		 * export default defineConfig({
		 *   env: {
		 *     schema: {
		 *       // ...
		 *     },
		 *     validateSecrets: true
		 *   }
		 * })
		 * ```
		 */
		validateSecrets?: boolean;
	};

	/**
	 *
	 * @kind heading
	 * @name Legacy Flags
	 * @description
	 * To help some users migrate between versions of Astro, we occasionally introduce `legacy` flags.
	 * 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?: Record<string, never>; // Currently no legacy flags are available.

	/**
	 *
	 * @kind heading
	 * @name Experimental Flags
	 * @description
	 * Astro offers experimental flags to give users early access to new features.
	 * These flags are not guaranteed to be stable.
	 */