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

Code before:
		 * @type {boolean}
		 * @default `false`
		 * @version 5.12
		 * @description
		 *
		 * Disables coercion of `import.meta.env` values that are populated from `process.env`, allowing you to use the raw value.
		 *
		 * By default, Astro converts your environment variables used through `import.meta.env` in some cases, and this 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).
		 *
		 * 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 raw environment variables guide](https://docs.astro.build/en/reference/experimental-flags/raw-env-values/) for more information.
		 */
		rawEnvValues?: boolean;
		/**
		 * @name experimental.chromeDevtoolsWorkspace
		 * @type {boolean}
		 * @default `false`
		 * @version 5.13
		 * @description
		 *
		 * Enables Chrome DevTools workspace integration for the Astro dev server.
		 *
		 * When enabled, the dev server will automatically configure a Chrome DevTools workspace for your project,
		 * allowing you to edit files directly in the browser and have those changes reflected in your local file system.
		 *
		 * ```js
		 * import { defineConfig } from 'astro/config';
		 *
		 * export default defineConfig({
		 *   experimental: {
		 *     chromeDevtoolsWorkspace: true,
		 *   },
		 * });
		 * ```
		 *
		 * See the [Chrome DevTools workspace documentation](https://developer.chrome.com/docs/devtools/workspaces) for more information.
		 */
		chromeDevtoolsWorkspace?: boolean;
	};
}

/**
 * Resolved Astro Config
 *
 * Config with user settings along with all defaults filled in.
 */
export interface AstroConfig extends AstroConfigType {
	// Public:

Review comment (suggestion):
```suggestion
		 * When enabled, the dev server will automatically configure a [Chrome DevTools workspace](https://developer.chrome.com/docs/devtools/workspaces) for your project,
```
Let's inline this link to define what the workspaces are, and let the "see more info" be the link to our own experimental docs, where we are free to add more specific Astro stuff as we need.

Code after:
		 * @type {boolean}
		 * @default `false`
		 * @version 5.12
		 * @description
		 *
		 * Disables coercion of `import.meta.env` values that are populated from `process.env`, allowing you to use the raw value.
		 *
		 * By default, Astro converts your environment variables used through `import.meta.env` in some cases, and this 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).
		 *
		 * 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 raw environment variables guide](https://docs.astro.build/en/reference/experimental-flags/raw-env-values/) for more information.
		 */
		rawEnvValues?: boolean;
		/**
		 * @name experimental.chromeDevtoolsWorkspace
		 * @type {boolean}
		 * @default `false`
		 * @version 5.13
		 * @description
		 *
		 * Enables Chrome DevTools workspace integration for the Astro dev server.
		 *
		 * When enabled, the dev server will automatically configure a [Chrome DevTools workspace](https://developer.chrome.com/docs/devtools/workspaces) for your project,
		 * allowing you to edit files directly in the browser and have those changes reflected in your local file system.
		 *
		 * ```js
		 * import { defineConfig } from 'astro/config';
		 *
		 * export default defineConfig({
		 *   experimental: {
		 *     chromeDevtoolsWorkspace: true,
		 *   },
		 * });
		 * ```
		 *
		 * See the [experimental Chrome DevTools workspace feature documentation](https://docs.astro.build/en/reference/experimental-flags/chrome-devtools-workspace/) for more information.
		 */
		chromeDevtoolsWorkspace?: boolean;
	};
}

/**
 * Resolved Astro Config
 *
 * Config with user settings along with all defaults filled in.
 */
export interface AstroConfig extends AstroConfigType {
	// Public: