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

Code before:
	 */
	compressHTML?: boolean;

	/**
	 * @docs
	 * @name scopedStyleStrategy
	 * @type {('where' | 'class' | 'attribute')}
	 * @default `'attribute'`
	 * @version 2.4
	 * @description
	 *
	 * Specify the strategy used for scoping styles within Astro components. Choose from:
	 *   - `'where'` 		- Use `:where` selectors, causing no specificity increase.
	 *   - `'class'` 		- Use class-based selectors, causing a +1 specificity increase.
	 *   - `'attribute'` 	- Use `data-` attributes, causing a +1 specificity increase.
	 *
	 * Using `'class'` is helpful when you want to ensure that element selectors within an Astro component override global style defaults (e.g. from a global stylesheet).
	 * Using `'where'` gives you more control over specificity, but requires that you use higher-specificity selectors, layers, and other tools to control which selectors are applied.
	 * 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 {'warning' | 'error' | 'ignore'}
	 * @default `'warning'`
	 * @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
	 * - `warning` (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?: 'warning' | 'error' | 'ignore';

	/**
	 * @docs
	 * @name security
	 * @type {Record<"checkOrigin", boolean> | undefined}
	 * @default `{checkOrigin: true}`
	 * @version 4.9.0
	 * @description
	 *
	 * Enables security measures for an Astro website.
	 *
	 * These features only exist for pages rendered on demand (SSR) using `server` mode or pages that opt out of prerendering in `static` mode.
	 *
	 * By default, Astro will automatically check that the “origin” header
	 * matches the URL sent by each request in on-demand rendered pages. You can
	 * disable this behavior by setting `checkOrigin` to `false`:

Review comment (suggestion):
```suggestion
	 * @type {'warn' | 'error' | 'ignore'}
```

Code after:
	 */
	compressHTML?: boolean;

	/**
	 * @docs
	 * @name scopedStyleStrategy
	 * @type {('where' | 'class' | 'attribute')}
	 * @default `'attribute'`
	 * @version 2.4
	 * @description
	 *
	 * Specify the strategy used for scoping styles within Astro components. Choose from:
	 *   - `'where'` 		- Use `:where` selectors, causing no specificity increase.
	 *   - `'class'` 		- Use class-based selectors, causing a +1 specificity increase.
	 *   - `'attribute'` 	- Use `data-` attributes, causing a +1 specificity increase.
	 *
	 * Using `'class'` is helpful when you want to ensure that element selectors within an Astro component override global style defaults (e.g. from a global stylesheet).
	 * Using `'where'` gives you more control over specificity, but requires that you use higher-specificity selectors, layers, and other tools to control which selectors are applied.
	 * 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 security
	 * @type {Record<"checkOrigin", boolean> | undefined}
	 * @default `{checkOrigin: true}`
	 * @version 4.9.0
	 * @description
	 *
	 * Enables security measures for an Astro website.
	 *
	 * These features only exist for pages rendered on demand (SSR) using `server` mode or pages that opt out of prerendering in `static` mode.
	 *
	 * By default, Astro will automatically check that the “origin” header
	 * matches the URL sent by each request in on-demand rendered pages. You can
	 * disable this behavior by setting `checkOrigin` to `false`: