Astro v6.0

astro.sidebar.ts

@@ -90,6 +90,7 @@ export const sidebar = [
 					group('guides.upgrade.major', {
 						collapsed: true,
 						items: [
+							'guides/upgrade-to/v6',
 							'guides/upgrade-to/v5',
 							'guides/upgrade-to/v4',
 							'guides/upgrade-to/v3',
@@ -145,15 +146,9 @@ export const sidebar = [
 					'reference/experimental-flags',
 					'reference/experimental-flags/csp',
 					'reference/experimental-flags/fonts',
-					'reference/experimental-flags/live-content-collections',
 					'reference/experimental-flags/client-prerender',
 					'reference/experimental-flags/content-intellisense',
-					'reference/experimental-flags/preserve-scripts-order',
-					'reference/experimental-flags/heading-id-compat',
-					'reference/experimental-flags/static-import-meta-env',
 					'reference/experimental-flags/chrome-devtools-workspace',
-					'reference/experimental-flags/fail-on-prerender-conflict',
-					'reference/experimental-flags/svg-optimization',
 				],
 			}),
 			'reference/legacy-flags',

src/content/docs/de/tutorial/6-islands/4.mdx

@@ -119,7 +119,8 @@ Aktualisiere Astro und alle Integrationen auf die neuesten Versionen, indem du i
 
     ```ts title="src/content.config.ts"
     import { glob } from "astro/loaders";
-    import { z, defineCollection } from "astro:content";
+    import { defineCollection } from "astro:content";
+    import { z } from "astro/zod";
 
     const blog = defineCollection({
         loader: glob({ pattern: '**/[^_]*.md', base: "./src/blog" }),
@@ -148,7 +149,7 @@ Aktualisiere Astro und alle Integrationen auf die neuesten Versionen, indem du i
 1. Erstelle eine neue Seiten­datei `src/pages/posts/[...slug].astro`.  
    Markdown- und MDX-Dateien werden innerhalb einer Sammlung nicht mehr automatisch zu Seiten. Du musst daher eine Seite erstellen, die für die Ausgabe jedes einzelnen Blogbeitrags verantwortlich ist.
 
-2. Füge den folgenden Code ein, um deine Sammlung [abzufragen](/de/guides/content-collections/#querying-collections) und für jede generierte Seite die `slug` und den Seiteninhalt bereitzustellen:
+2. Füge den folgenden Code ein, um deine Sammlung [abzufragen](/de/guides/content-collections/#querying-build-time-collections) und für jede generierte Seite die `slug` und den Seiteninhalt bereitzustellen:
 
     ```astro title="src/pages/posts/[...slug].astro"
     ---

src/content/docs/en/getting-started.mdx

@@ -5,6 +5,9 @@ i18nReady: true
 tableOfContents: false
 editUrl: false
 next: false
+banner:
+  content: |
+    Astro v6 is here! <a href="/en/guides/upgrade-to/v6/">Learn how to upgrade your site</a>
 hero:
   title: Astro Docs
   tagline: Guides, resources, and API references to help you build with Astro.

src/content/docs/en/guides/cms/keystatic.mdx

@@ -183,7 +183,7 @@ Visit `http://127.0.0.1:4321/keystatic` in the browser to see the Keystatic Admi
 
 ## Rendering Keystatic content
 
-Use Astro's Content Collections API to [query and display your posts and collections](/en/guides/content-collections/#querying-collections), just as you would in any Astro project.
+[Query and display your posts and collections](/en/guides/content-collections/#querying-build-time-collections), just as you would in any Astro project.
 
 ### Displaying a collection list
 

src/content/docs/en/guides/deploy/microsoft-azure.mdx

@@ -40,7 +40,7 @@ The GitHub action yaml that is created for you assumes the use of node 14. This
 
 ```
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=22.12.0"
   },
 ```
 

src/content/docs/en/guides/deploy/netlify.mdx

@@ -101,7 +101,7 @@ You can also create a new site on Netlify and link up your Git repository by ins
 
 ### Set a Node.js version
 
-If you are using a legacy [build image](https://docs.netlify.com/configure-builds/get-started/#build-image-selection) (Xenial) on Netlify, make sure that your Node.js version is set. Astro requires `v18.20.8` or `v20.3.0` or higher.
+If you are using a legacy [build image](https://docs.netlify.com/configure-builds/get-started/#build-image-selection) (Xenial) on Netlify, make sure that your Node.js version is set. Astro requires `v22.12.0` or higher.
 
 You can [specify your Node.js version in Netlify](https://docs.netlify.com/configure-builds/manage-dependencies/#node-js-and-javascript) using:
 - a [`.nvmrc`](https://github.com/nvm-sh/nvm#nvmrc) file in your base directory.

src/content/docs/en/guides/endpoints.mdx

@@ -47,6 +47,8 @@ import type { APIRoute } from "astro";
 export const GET: APIRoute = async ({ params, request }) => {...}
 ```
 
+Note that endpoints whose URLs include a file extension (e.g. `src/pages/sitemap.xml.ts`) can only be accessed without a trailing slash (e.g. `/sitemap.xml`), regardless of your [`build.trailingSlash`](/en/reference/configuration-reference/#trailingslash) configuration.
+
 ### `params` and Dynamic routing
 
 Endpoints support the same [dynamic routing](/en/guides/routing/#dynamic-routes) features that pages do. Name your file with a bracketed parameter name and export a [`getStaticPaths()` function](/en/reference/routing-reference/#getstaticpaths). Then, you can access the parameter using the `params` property passed to the endpoint function:

src/content/docs/en/guides/environment-variables.mdx

@@ -58,7 +58,6 @@ Astro includes a few environment variables out of the box:
 - `import.meta.env.DEV`: `true` if your site is running in development; `false` otherwise. Always the opposite of `import.meta.env.PROD`.
 - `import.meta.env.BASE_URL`: The base URL your site is being served from. This is determined by the [`base` config option](/en/reference/configuration-reference/#base).
 - `import.meta.env.SITE`: This is set to [the `site` option](/en/reference/configuration-reference/#site) specified in your project's `astro.config`.
-- `import.meta.env.ASSETS_PREFIX`: The prefix for Astro-generated asset links if the [`build.assetsPrefix` config option](/en/reference/configuration-reference/#buildassetsprefix) is set. This can be used to create asset links not handled by Astro.
 
 Use them like any other environment variable.
 

src/content/docs/en/guides/images.mdx

@@ -51,7 +51,7 @@ All native HTML tags, including `<img>` and `<svg>`, are also available in `.ast
 For all images in `.astro` files, **the value of the image `src` attribute is determined by the location of your image file**:
 
 - A local image from your project `src/` folder uses an import from the file's relative path.
-  
+
   The image and picture components use the named import directly (e.g. `src={rocket}`), while the `<img>` tag uses the `src` object property of the import (e.g. `src={rocket.src}`).
 
 - Remote and `public/` images use a URL path.
@@ -321,7 +321,7 @@ import myImage from '../assets/my_image.png'; // Image is 1600x900
 
 Responsive images are images that adjust to improve performance across different devices. These images can resize to fit their container, and can be served in different sizes depending on your visitor's screen size and resolution.
 
-With [responsive image properties](/en/reference/modules/astro-assets/#responsive-image-properties) applied to the `<Image />` or `<Picture />` components, Astro will automatically generate the required `srcset` and `sizes` values for your images, and apply the necessary [styles to ensure they resize correctly](#responsive-image-styles). 
+With the [layout property](/en/reference/modules/astro-assets/#layout) applied to the `<Image />` or `<Picture />` components, Astro will automatically generate the required `srcset` and `sizes` values for your images, and apply the necessary [styles to ensure they resize correctly](#responsive-image-styles).
 
 When this responsive behavior is [configured globally with `image.layout`](/en/reference/configuration-reference/#imagelayout), it will apply to all image components and also to any local and remote images using [the Markdown `![]()` syntax](/en/guides/images/#images-in-markdown-files).
 
@@ -396,7 +396,7 @@ The global styles applied by Astro will depend on the layout type, and are desig
 
 The styles use the [`:where()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:where), which has a [specificity](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_cascade/Specificity) of 0, meaning that it is easy to override with your own styles. Any CSS selector will have a higher specificity than `:where()`, so you can easily override the styles by adding your own styles to target the image.
 
-You can override the `object-fit` and `object-position` styles on a per-image basis by setting the `fit` and `position` props on the `<Image />` or `<Picture />` component. 
+You can override the `object-fit` and `object-position` styles on a per-image basis by setting the `fit` and `position` props on the `<Image />` or `<Picture />` component.
 
 #### Responsive images with Tailwind 4
 
@@ -590,8 +590,8 @@ This is a blog post
 The `image` helper for the content collections schema lets you validate and import the image.
 
 ```ts title="src/content.config.ts"
-import { defineCollection } from "astro:content";
-import { z } from "astro/zod";
+import { defineCollection } from 'astro:content';
+import { z } from 'astro/zod';
 
 const blogCollection = defineCollection({
 	schema: ({ image }) => z.object({

src/content/docs/en/guides/imports.mdx

@@ -344,7 +344,7 @@ Additionally, glob patterns must begin with one of the following:
 
 ### `import.meta.glob()` vs `getCollection()`
 
-[Content collections](/en/guides/content-collections/) provide a [`getCollection()` API](/en/reference/modules/astro-content/#getcollection) for loading multiple files instead of `import.meta.glob()`. If your content files (e.g. Markdown, MDX, Markdoc) are located in collections within the `src/content/` directory, use `getCollection()` to [query a collection](/en/guides/content-collections/#querying-collections) and return content entries.
+[Content collections](/en/guides/content-collections/) provide [performant, content-focused APIs](/en/reference/modules/astro-content/) for loading multiple files instead of `import.meta.glob()`. Use `getCollection()` and `getLiveCollection()` to query your collections and return content entries.
 
 ## WASM
 

src/content/docs/en/guides/integrations-guide/markdoc.mdx

@@ -113,7 +113,7 @@ Markdoc files can only be used within content collections. Add entries to any co
       - quick-start.mdoc
 </FileTree>
 
-Then, query your collection using the [Content Collection APIs](/en/guides/content-collections/#querying-collections):
+Then, [query and display your posts and collections](/en/guides/content-collections/#querying-build-time-collections):
 
 ```astro title="src/pages/why-markdoc.astro"
 ---

src/content/docs/en/guides/integrations-guide/mdx.mdx

@@ -96,9 +96,9 @@ It also adds extra features to standard MDX, including support for Markdown-styl
 
 `.mdx` files must be written in [MDX syntax](https://mdxjs.com/docs/what-is-mdx/#mdx-syntax) rather than Astro’s HTML-like syntax.
 
-### Using MDX with content collections
+### Using local MDX with content collections
 
-To include MDX files in a content collection, make sure that your [collection loader](/en/guides/content-collections/#defining-the-collection-loader) is configured to load content from `.mdx` files:
+To include your local MDX files in a content collection, make sure that your [collection loader](/en/guides/content-collections/#build-time-collection-loaders) is configured to load content from `.mdx` files:
 
 ```js title="src/content.config.ts" ins="mdx"
 import { defineCollection } from 'astro:content';

src/content/docs/en/guides/internationalization.mdx

@@ -170,15 +170,11 @@ Set this option when all routes will have their `/locale/` prefix in their URL a
 
 - URLs without a locale prefix, (e.g. `example.com/about/`) will return a 404 (not found) status code unless you specify a [fallback strategy](#fallback).
 
-### `redirectToDefaultLocale`
+#### Opting out of redirects for the home URL
 
-<p><Since v="4.2.0" /></p>
+Even with your default locale routes prefixed, this behaviour does not apply by default to your site's index page. This allows you to have a home page that exists outside of your configured locale structure, where all of your localized routes are prefixed except the home URL of your site.
 
-Configures whether or not the home URL (`/`) generated by `src/pages/index.astro` will redirect to `/<defaultLocale>`.
-
-Setting `prefixDefaultLocale: true` will also automatically set `redirectToDefaultLocale: true` in your `routing` config object. By default, the required `src/pages/index.astro` file will automatically redirect to the index page of your default locale.
-
-You can opt out of this behavior by [setting `redirectToDefaultLocale: false`](/en/reference/configuration-reference/#i18nroutingredirecttodefaultlocale). This allows you to have a site home page that exists outside of your configured locale folder structure.
+You can opt out of this behavior so that your main site URL will also redirect to a prefixed, localized route for your default locale. When `prefixDefaultLocale: true` is set, you can additionally configure `redirectToDefaultLocale: true`. This will ensure that the home URL (`/`) generated by `src/pages/index.astro` will redirect to `/[defaultLocale]/`.
 
 ### `manual`
 

src/content/docs/en/guides/markdown-content.mdx

@@ -399,7 +399,7 @@ When using the frontmatter `layout` property, you must include the `<meta charse
 
 Astro's internal Markdown processor is not available for processing remote Markdown.
 
-To fetch remote Markdown for use in [content collections](/en/guides/content-collections/), you can [build a custom loader](/en/guides/content-collections/#building-a-custom-loader) with access to a [`renderMarkdown()` function](/en/reference/content-loader-reference/#rendermarkdown).
+To fetch remote Markdown for use in [content collections](/en/guides/content-collections/), you can [build a custom loader](/en/guides/content-collections/#custom-build-time-loaders) with access to a [`renderMarkdown()` function](/en/reference/content-loader-reference/#rendermarkdown).
 
 To fetch remote Markdown directly and render it to HTML, you will need to install and configure your own Markdown parser from NPM. This will not inherit from any of Astro's built-in Markdown settings that you have configured.
 

src/content/docs/en/guides/media/cloudinary.mdx

@@ -134,7 +134,7 @@ export const collections = {
 }
 ```
 
-You can then use the [`getCollection()` or `getEntry()` query functions](/en/guides/content-collections/#querying-collections) to select one or many images or videos from your collection.
+You can then use the [`getCollection()` or `getEntry()` query functions](/en/guides/content-collections/#querying-build-time-collections) to select one or many images or videos from your collection.
 
 See [Cloudinary's `cldAssetsLoader` documentation](https://astro.cloudinary.dev/cldassetsloader/basic-usage) for more information.
 

src/content/docs/en/guides/migrate-to-astro/from-create-react-app.mdx

@@ -349,7 +349,7 @@ const randomUser = data.results[0];
 ---
 ```
 
-See more about local files imports with [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [querying using the Collections API](/en/guides/content-collections/#querying-collections) or [fetching remote data](/en/guides/data-fetching/).
+See more about local files imports with [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [querying with content collections](/en/guides/content-collections/#querying-build-time-collections) or [fetching remote data](/en/guides/data-fetching/).
 
 ### CRA Styling to Astro
 

src/content/docs/en/guides/migrate-to-astro/from-gatsby.mdx

@@ -36,7 +36,7 @@ When you rebuild your Gatsby site in Astro, you will notice some important diffe
 
 - [Astro components](/en/basics/astro-components/) are not written as exported functions that return page templating. Instead, you'll split your code into a "code fence" for your JavaScript and a body exclusively for the HTML you generate.
 
-- [Local file data](/en/guides/imports/): Gatsby uses GraphQL to retrieve data from your project files. Astro uses ESM imports and top-level await functions (e.g. [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [`getCollection()`](/en/guides/content-collections/#querying-collections)) to import data from your project files. You can manually add GraphQL to your Astro project but it is not included by default.
+- [Local file data](/en/guides/imports/): Gatsby uses GraphQL to retrieve data from your project files. Astro uses ESM imports and top-level await functions (e.g. [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [`getCollection()`](/en/guides/content-collections/#querying-build-time-collections)) to import data from your project files. You can manually add GraphQL to your Astro project but it is not included by default.
 
 ## Convert your Gatsby Project
 

src/content/docs/en/guides/migrate-to-astro/from-nextjs.mdx

@@ -405,7 +405,7 @@ const randomUser = data.results[0];
 ---
 ```
 
-See more about local files imports with [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [querying using the Collections API](/en/guides/content-collections/#querying-collections) or [fetching remote data](/en/guides/data-fetching/).
+See more about local files imports with [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [querying with content collections](/en/guides/content-collections/#querying-build-time-collections) or [fetching remote data](/en/guides/data-fetching/).
 
 ### Next Styling to Astro
 

src/content/docs/en/guides/upgrade-to/v5.mdx

@@ -1112,7 +1112,7 @@ function useRoute(route: IntegrationRouteData) {
 }
 ```
 
-<ReadMore>See the [API reference for `IntegrationRouteData`](/en/reference/integrations-reference/#integrationroutedata-type-reference).</ReadMore>
+<ReadMore>See the API reference for `IntegrationRouteData`.</ReadMore>
 
 ### Changed: `distURL` is now an array (Integrations API)
 
@@ -1139,7 +1139,7 @@ if (route.distURL) {
 }
 ```
 
-<ReadMore>See the [API reference for `IntegrationRouteData`](/en/reference/integrations-reference/#integrationroutedata-type-reference).</ReadMore>
+<ReadMore>See the API reference for `IntegrationRouteData`.</ReadMore>
 
 ### Changed: Arguments passed to `app.render()` (Adapter API)