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

Code before:
		 *   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?: {
		/**
		 * Enable backwards compatibility for v5 content collections.
		 *
		 * When enabled, restores the following v5 behaviors:
		 * - Allows legacy config file location: `src/content/config.ts`
		 * - Allows collections without explicit loaders (automatically wraps with glob loader)
		 * - Supports `type: 'content'` and `type: 'data'` without loaders
		 * - Preserves legacy entry API: `entry.slug` and `entry.render()`
		 * - Uses path-based entry IDs instead of slug-based IDs
		 *
		 * This is a temporary migration helper for projects upgrading to v6.
		 * Migrate collections to the Content Layer API, then disable this flag.
		 *
		 * @type {boolean}
		 * @default false
		 */
		collectionsBackwardsCompat?: boolean;
	};

	/**
	 *
	 * @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.
	 */
	experimental?: {
		/**

Review comment (suggestion):
```suggestion
		 * Enable backwards compatibility for v4 content collections.
		 *
		 * When enabled, restores the following v4 behaviors:
```

Code after:
	};

	/**
	 *
	 * @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?: {
		/**
		 * Enable backwards compatibility for v4 content collections.
		 *
		 * When enabled, restores the following v4 behaviors:
		 * - Allows legacy config file location: `src/content/config.ts`
		 * - Allows collections without explicit loaders (automatically wraps with glob loader)
		 * - Supports `type: 'content'` and `type: 'data'` without loaders
		 * - Preserves legacy entry API: `entry.slug` and `entry.render()`
		 * - Uses path-based entry IDs instead of slug-based IDs
		 *
		 * This is a temporary migration helper for projects upgrading to v6.
		 * Migrate collections to the Content Layer API, then disable this flag.
		 *
		 * @type {boolean}
		 * @default false
		 */
		collectionsBackwardsCompat?: boolean;
	};

	/**
	 *
	 * @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.
	 */
	experimental?: {
		/**
		 *
		 * @name experimental.clientPrerender
		 * @type {boolean}
		 * @default `false`
		 * @version 4.2.0
		 * @description
		 * Enables pre-rendering your prefetched pages on the client in supported browsers.
		 *
		 * This feature uses the experimental [Speculation Rules Web API](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API) and enhances the default `prefetch` behavior globally to prerender links on the client.
		 * You may wish to review the [possible risks when prerendering on the client](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API#unsafe_prefetching) before enabling this feature.