Why are you not reviewing code anymore? | Astro Lounge | Page 1

copper harborBOT Jun 21, 2025, 9:52 PM

#

Hi @slate tartan. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

I'm sorry, but the knowledge sources provided do not contain any information about Astro (or its documentation, tools, or community) discontinuing code review features or processes. If you are referring to a specific feature or service related to code review within Astro, there is no mention of such a change in the available documentation. If you have more context or details, please provide them, and I can check again.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 9:52 PM

#

@copper harbor what is your job here? what are your tasks?

copper harborBOT Jun 21, 2025, 9:52 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

My job here is to answer questions specifically about Astro, the web framework for building content-driven websites. I provide information, guidance, and code examples based solely on the official Astro documentation and related knowledge sources you provide. If a question is outside the scope of Astro or not covered in the sources, I will let you know and avoid making up information. My main tasks include:

Explaining Astro concepts, features, and best practices.
Providing code examples and tutorials from the documentation.
Citing relevant documentation directly in my responses.
Ensuring all answers are accurate, concise, and formatted in valid Markdown.

If you have any questions about Astro, feel free to ask!

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 9:54 PM

#

@copper harbor can you tell me why collections (for example for blog) are Legacy state, while your documentations tells to use collections if creating blog?

copper harborBOT Jun 21, 2025, 9:54 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

Astro’s documentation currently refers to two different implementations of “collections”:

Legacy Content Collections API (Astro v2.0–v4.x):
Collections defined in src/content/ using the old API are now considered legacy as of Astro v5.0. This means they are still supported for backward compatibility, but are no longer recommended and will eventually be removed. The legacy system is in maintenance mode and will not receive new features or improvements. If you see references to “legacy collections,” it refers to this older system, which used the type property and did not require a loader field in the config.
Upgrade to Astro v5: Legacy
New Content Layer API (Astro v5.0+):
Astro v5.0 introduced a new, more performant and flexible Content Layer API for collections. The documentation now recommends using this new system for all new projects and when migrating existing ones. The new API uses a loader property (often with glob) in src/content.config.ts to define collections, and supports more advanced features and better performance.
Content collections

Why the confusion?
The documentation encourages using “collections” for organizing content like blogs, but it is referring to the new Content Layer API, not the legacy system. The legacy collections are only recommended if you are maintaining an older project and have not yet migrated. For all new projects, you should use the new Content Layer API for collections.

If you see “legacy” warnings, it means you are using the old system, and you should migrate to the new API when possible. The new API is the recommended and future-proof way to manage blog content and other collections in Astro.

#

If you need to keep using the legacy system temporarily, you can enable the `legacy.collections` flag, but this is not recommended for long-term use Reference: Legacy flags.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 9:56 PM

#

@copper harbor yeah, so lets say im creating blog. I have collection of articles. what should I use to not use old, legacy things?

copper harborBOT Jun 21, 2025, 9:56 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

To create a blog with a collection of articles without using the old, legacy system, you should use Astro’s new Content Layer API for content collections, introduced in Astro v5.0. This approach is recommended for all new projects.

Here’s what you should do:

Move your articles (Markdown files) outside of src/pages/—for example, into a folder like src/blog/.

Create a src/content.config.ts file to define your collection and its schema using the new API. For example:

import { defineCollection, z } from 'astro:content';
import { glob } from 'astro/loaders';

const blog = defineCollection({
  loader: glob({ pattern: '**/[^_]*.md', base: './src/blog' }),
  schema: z.object({
    title: z.string(),
    pubDate: z.date(),
    description: z.string(),
    author: z.string(),
    image: z.object({
      url: z.string(),
      alt: z.string()
    }),
    tags: z.array(z.string())
  })
});

export const collections = { blog };

Create a collection for your posts

Use getCollection() to query your articles in your pages or components:
```
import { getCollection } from "astro:content";
const allPosts = await getCollection("blog");
```
Replace import.meta.glob() with getCollection()

#

This method uses the new Content Layer API and avoids the legacy system. You do not need to use the `legacy.collections` flag or the old `type: 'content'` property. The new API is more performant, flexible, and future-proof Defining Collections.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 9:57 PM

#

@copper harbor that is exactly what I did. and to be able to use these collections I need to set this option in astro settings:

legacy: {
collections: true,
},

Why? Why I should do that? Are you able to answer me?

copper harborBOT Jun 21, 2025, 9:57 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

If you are using the new Content Layer API for collections (with a loader property in src/content.config.ts and your content outside of src/content/), you should NOT need to set legacy: { collections: true } in your Astro config. The legacy.collections flag is only required if you are still using the old, legacy collections system (collections in src/content/ using the type property and without a loader).

According to the documentation:

The legacy.collections flag enables legacy behavior for content collections as used in Astro v2 through v4. If enabled, only collections with type: 'content' or type: 'data' in src/content/ are handled using the legacy implementation. Collections using the new Content Layer API (with a loader defined) do not require this flag and should not be in src/content/ Legacy flags.
If you are using the new API and still need to set the legacy flag for your collections to work, this suggests that either your collection files are in the wrong location (e.g., still in src/content/), or your configuration is not fully migrated to the new API.

Summary:
You should only need the legacy.collections flag if you are using the old, legacy collections system. For the new Content Layer API, place your content outside src/content/, define a loader in src/content.config.ts, and you do not need the legacy flag. If you still need the flag, double-check your file locations and configuration, as this is not the intended behavior for the new system.

#

If you are following all the new API steps and still require the flag, the knowledge sources do not provide an explanation for this and it may indicate a misconfiguration or an edge case not covered in the documentation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 10:00 PM

#

@copper harbor all my artricles are in /src/content/articles

in /src dir i have this config file

import { defineCollection, z } from 'astro:content';
import { glob } from 'astro/loaders';

const articles = defineCollection({
loader: glob({ base: '@/content/articles', pattern: '**/*.{md,mdx}' }),
schema: z.object({
title: z.string(),
description: z.string(),
created: z.coerce.date(),
updated: z.coerce.date().optional(),
tags: z.array(z.string()).optional(),
icon: z.string().optional(),
draft: z.boolean().optional(),
author: z.string().optional(),
}),
});

export const collections = { articles };

copper harborBOT Jun 21, 2025, 10:00 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

Based on your setup:

Your articles are in /src/content/articles
Your src/content.config.ts uses the new Content Layer API with a loader and schema

According to the official Astro documentation:

Collections using the new Content Layer API (with a loader defined) should not be placed inside src/content/. The src/content/ directory is reserved for legacy collections. If you place your content there, Astro expects legacy behavior, and you may be required to enable the legacy.collections flag for it to work Legacy flags.
For the new API, your content (e.g., articles) should be outside of src/content/, such as src/articles/ or another directory. Collections using the Content Layer API are forbidden in src/content/, but may exist anywhere else in your project.

What you should do:

Move your articles from /src/content/articles to another directory, such as /src/articles.

Update your loader base path accordingly:

loader: glob({ base: './src/articles', pattern: '**/*.{md,mdx}' })

Remove the legacy.collections flag from your config.

Summary:
You are being required to use the legacy.collections flag because your content is inside src/content/, which is reserved for legacy collections. Move your content outside of src/content/ to use the new Content Layer API without the legacy flag Legacy flags.

If you follow this structure, you will not need the legacy flag, and your project will use the recommended, future-proof approach.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 10:15 PM

#

@copper harbor ok,. but what is the modern way to render, for exaple list of articles thatg i have i new, awesome, shiny /src/articles?

copper harborBOT Jun 21, 2025, 10:15 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

The modern way to render a list of articles in Astro, using the new Content Layer API (with your articles in a directory like /src/articles), is to use the getCollection() helper from astro:content. This function fetches all entries from your defined collection, and you can then map over them in your Astro page to display the list.

Here’s an example based on the official documentation:

---
// Import the helper
import { getCollection } from 'astro:content';

// Fetch all articles from your 'articles' collection
const posts = await getCollection('articles');
---
<h1>My Articles</h1>
<ul>
  {posts.map(post => (
    <li>
      <a href={`/articles/${post.id}`}>{post.data.title}</a>
    </li>
  ))}
</ul>

getCollection('articles') will return all your articles as defined in your content.config.ts.
You can access each article’s metadata (like title) via post.data.title.
The id property is used to generate the link to each article’s page.

This approach is the recommended, modern way to render a list of articles using Astro’s new content collections system Querying Collections.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 10:28 PM

#

@copper harbor is something wrong with my content.config.ts located in components directory?

import { defineCollection, z } from "astro:content";
import { glob } from "astro/loaders";

const articles = defineCollection({
loader: glob({ base: "@/articles", pattern: "**/*.{md,mdx}" }),
schema: z.object({
title: z.string(),
description: z.string(),
created: z.coerce.date(),
updated: z.coerce.date().optional(),
tags: z.array(z.string()).optional(),
icon: z.string().optional(),
draft: z.boolean().optional(),
author: z.string().optional(),
}),
});

export const collections = { articles };

copper harborBOT Jun 21, 2025, 10:28 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

Yes, there is an issue with your content.config.ts location. According to the official Astro documentation, the content collections config file must be located at the root of your src/ directory and named content.config.ts (or .js/.mjs). Placing it in the components directory is not supported and Astro will not recognize your collections if you do so.

To define collections, you must create a src/content.config.ts file in your project (.js and .mjs extensions are also supported). This is a special file that Astro will use to configure your content collections based on the following structure
Defining Collections

What you should do:
Move your `content.config.ts` file from the `components` directory to the root of your `src/` directory (i.e., `src/content.config.ts`). This will allow Astro to properly detect and use your content collections configuration.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 10:30 PM

#

@copper harbor I did it, and when trying to list all my articles, I dont see any

copper harborBOT Jun 21, 2025, 10:30 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

If you have moved your content.config.ts to src/content.config.ts and your articles to a directory like src/articles/, but you still do not see any articles when listing them with getCollection('articles'), here are the key things to check based on the official Astro documentation:

File Locations:
- Your config file must be at src/content.config.ts.
- Your articles should be in src/articles/ (not in src/content/).
Loader Base Path:
- In your config, the base property in the glob loader should be a relative path from the project root, such as ./src/articles:
```
loader: glob({ base: './src/articles', pattern: '**/*.{md,mdx}' })
```
- Using @/articles is not documented as a supported path in the knowledge sources.
Restart the Dev Server:
- After making changes to your content config or moving files, you must restart the Astro dev server for changes to take effect Create a collection for your posts.
Querying the Collection:
- Use getCollection('articles') in your Astro page/component to fetch the articles Querying Collections.

If you have followed all these steps and still do not see any articles, the knowledge sources do not provide further troubleshooting steps for this scenario. There may be an issue not covered in the documentation, such as a typo in the collection name, file extensions, or schema mismatch.

Summary:

Ensure your config is at src/content.config.ts.
Use base: './src/articles' in your loader.
Place your articles in src/articles/.
Restart the dev server after changes.

#

If you have done all of the above and the issue persists, the knowledge sources do not contain enough information to diagnose the problem further.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 10:34 PM

#

@copper harbor my "content.config.ts" is in /src directory and looks like this:

import { defineCollection, z } from "astro:content";
import { glob } from "astro/loaders";

const articles = defineCollection({
loader: glob({ base: "@/articles", pattern: "**/*.{md,mdx}" }),
schema: z.object({
title: z.string(),
description: z.string(),
created: z.coerce.date(),
updated: z.coerce.date().optional(),
tags: z.array(z.string()).optional(),
icon: z.string().optional(),
draft: z.boolean().optional(),
author: z.string().optional(),
}),
});

export const collections = { articles };

My index.astro for listing all articles looks like this:

import { getCollection } from 'astro:content';
import { siteTitle, siteDescription } from '../consts';
import Footer from '../components/Footer.astro';
// import FormattedDate from '../components/FormattedDate.astro';
import Head from '../components/Head.astro';
import Header from '../components/Header.astro';
import Icon from '@xtreat/astro-iconify';
import MainProse from '../components/MainProse.astro';
import ThemeSwitcher from '../components/ThemeSwitcher.astro';
import ThemeWrapper from '../components/ThemeWrapper.astro';

const articles = await getCollection('articles');

const sortedArticles = [...articles].sort((a, b) => {
const dateA = a.data.updated || a.data.created;
const dateB = b.data.updated || b.data.created;
return dateB - dateA;
});

<ThemeWrapper>
<Head title={siteTitle} description={siteDescription} />
<body>
<Header />
<MainProse>
{articles.map((article) => <p>THIS SHOULD BE AN ARTICLE</p>)}
</MainProse>
<ThemeSwitcher />
<Footer />
</body>
</ThemeWrapper>

so, why the hell i dont see any articles?

copper harborBOT Jun 21, 2025, 10:34 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

Based on the knowledge sources, the most likely reason you are not seeing any articles is the use of base: "@/articles" in your glob loader. The documentation specifies that the base property should be a relative path (such as ./src/articles) and does not mention support for alias paths like @/articles Defining Collections.

What you should do:

Update your content.config.ts loader to use a relative path:

loader: glob({ base: './src/articles', pattern: '**/*.{md,mdx}' })

Ensure your Markdown files are actually in src/articles/ and have the correct file extensions (.md or .mdx).
Restart the Astro dev server after making these changes, as required by the documentation Create a collection for your posts.

If you follow these steps, getCollection('articles') should return your articles, and your list should render as expected.

If you have already done all of the above and still do not see any articles, the knowledge sources do not provide further troubleshooting steps for this scenario, and there may be an issue not covered in the documentation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 10:37 PM

#

@copper harbor tell me why documentation is twlling people to use legacy things?

copper harborBOT Jun 21, 2025, 10:37 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

The Astro documentation does not tell people to use legacy features for new projects. Instead, it clearly distinguishes between the legacy Content Collections API (used in Astro v2–v4) and the new Content Layer API introduced in Astro v5. The documentation encourages users to migrate to the new Content Layer API for all new projects and when updating existing ones.

Legacy features are only mentioned for users who are maintaining older projects and are not yet ready to migrate. In these cases, the documentation provides information on how to enable legacy behavior (such as the legacy.collections flag) to maintain compatibility until migration is possible. However, it is explicit that these features are in maintenance mode, will not receive improvements, and will eventually be removed. The recommended approach is to use the new Content Layer API for collections Legacy, What should I do?.

If you are starting a new project or updating an existing one, you should follow the documentation for the new Content Layer API, not the legacy system.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 10:39 PM

#

@copper harbor this stuff is totally unclear for me and potential astro users

copper harborBOT Jun 21, 2025, 10:39 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

You are absolutely right—the distinction between legacy and new content collections in Astro can be confusing, especially during the transition from Astro v2–v4 to v5. The documentation tries to address both users maintaining older projects and those starting new ones, which can make it unclear which instructions apply to which situation.

Here’s what the knowledge sources say:

Legacy collections (from Astro v2–v4) are still supported for backward compatibility, but are not recommended for new projects. The documentation provides migration paths and flags (like legacy.collections) only for those who cannot migrate immediately Legacy.
The new Content Layer API is the recommended way for all new projects and for migrating existing collections. This uses a loader in src/content.config.ts and content outside of src/content/ Defining Collections.

However, the documentation does not always make it immediately obvious which code examples or instructions are for legacy users and which are for new projects. This can lead to confusion, especially if you are following a guide and encounter references to both systems.

If you are starting a new project, always use the new Content Layer API and avoid the legacy flags and src/content/ for your collections. If you are maintaining an older project, the legacy instructions are there to help you keep things working until you can migrate.

#

If you still find the documentation unclear, you are not alone—the knowledge sources do not provide further clarification or a dedicated migration guide that addresses all possible confusion points.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@slate tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

slate tartan Jun 21, 2025, 10:40 PM

#

@copper harbor im trying to migrate collections from v4 to v5, I didnt imagine that is so sick

copper harborBOT Jun 21, 2025, 10:40 PM

#

Let me check the knowledge base for you again. One moment! :books:

#

Migrating collections from Astro v4 to v5 can indeed be challenging, and the documentation acknowledges that there are breaking changes and new concepts to learn. The main points to keep in mind from the official upgrade guide are:

Astro v5 introduces a new Content Layer API for collections, which is more performant and flexible, but requires changes to how collections are defined and where your content lives.
Legacy collections (the v2–v4 system, with content in src/content/ and using the type property) are now in maintenance mode. They can still work if you enable the legacy.collections flag, but this is only a temporary solution and not recommended for new work Legacy flags.
To migrate:
- Move your content out of src/content/ (e.g., to src/articles/).
- Create or update src/content.config.ts to use the new loader property with glob.
- Update your code to use getCollection() and reference the new id property instead of slug What should I do?.
- Remove the legacy.collections flag once you are fully migrated.

The documentation provides step-by-step instructions, but it does not hide that there are breaking changes and some manual work involved. If you encounter issues, double-check the file locations, loader paths, and that you have restarted the dev server after changes. If you still have trouble, the knowledge sources do not provide more detailed troubleshooting, and you may need to consult the Astro community for edge cases.

#

#Why are you not reviewing code anymore?

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you have any questions about Astro, feel free to ask!

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you need to keep using the legacy system temporarily, you can enable the `legacy.collections` flag, but this is not recommended for long-term use Reference: Legacy flags.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

This method uses the new Content Layer API and avoids the legacy system. You do not need to use the `legacy.collections` flag or the old `type: 'content'` property. The new API is more performant, flexible, and future-proof Defining Collections.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you are following all the new API steps and still require the flag, the knowledge sources do not provide an explanation for this and it may indicate a misconfiguration or an edge case not covered in the documentation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you follow this structure, you will not need the legacy flag, and your project will use the recommended, future-proof approach.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

This approach is the recommended, modern way to render a list of articles using Astro’s new content collections system Querying Collections.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

What you should do:
Move your `content.config.ts` file from the `components` directory to the root of your `src/` directory (i.e., `src/content.config.ts`). This will allow Astro to properly detect and use your content collections configuration.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you have done all of the above and the issue persists, the knowledge sources do not contain enough information to diagnose the problem further.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

const sortedArticles = [...articles].sort((a, b) => {
const dateA = a.data.updated || a.data.created;
const dateB = b.data.updated || b.data.created;
return dateB - dateA;
});

If you have already done all of the above and still do not see any articles, the knowledge sources do not provide further troubleshooting steps for this scenario, and there may be an issue not covered in the documentation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you are starting a new project or updating an existing one, you should follow the documentation for the new Content Layer API, not the legacy system.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you still find the documentation unclear, you are not alone—the knowledge sources do not provide further clarification or a dedicated migration guide that addresses all possible confusion points.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

Migrating can be frustrating, but once you are on the new system, you will benefit from better performance and future support Upgrade to Astro v5.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#Why are you not reviewing code anymore?

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you have any questions about Astro, feel free to ask!

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you need to keep using the legacy system temporarily, you can enable the legacy.collections flag, but this is not recommended for long-term use Reference: Legacy flags.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

This method uses the new Content Layer API and avoids the legacy system. You do not need to use the legacy.collections flag or the old type: 'content' property. The new API is more performant, flexible, and future-proof Defining Collections.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you are following all the new API steps and still require the flag, the knowledge sources do not provide an explanation for this and it may indicate a misconfiguration or an edge case not covered in the documentation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you follow this structure, you will not need the legacy flag, and your project will use the recommended, future-proof approach.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

This approach is the recommended, modern way to render a list of articles using Astro’s new content collections system Querying Collections.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

What you should do: Move your content.config.ts file from the components directory to the root of your src/ directory (i.e., src/content.config.ts). This will allow Astro to properly detect and use your content collections configuration.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you have done all of the above and the issue persists, the knowledge sources do not contain enough information to diagnose the problem further.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

const sortedArticles = [...articles].sort((a, b) => { const dateA = a.data.updated || a.data.created; const dateB = b.data.updated || b.data.created; return dateB - dateA; });

If you have already done all of the above and still do not see any articles, the knowledge sources do not provide further troubleshooting steps for this scenario, and there may be an issue not covered in the documentation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you are starting a new project or updating an existing one, you should follow the documentation for the new Content Layer API, not the legacy system.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you still find the documentation unclear, you are not alone—the knowledge sources do not provide further clarification or a dedicated migration guide that addresses all possible confusion points.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

Migrating can be frustrating, but once you are on the new system, you will benefit from better performance and future support Upgrade to Astro v5.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you need to keep using the legacy system temporarily, you can enable the `legacy.collections` flag, but this is not recommended for long-term use Reference: Legacy flags.

This method uses the new Content Layer API and avoids the legacy system. You do not need to use the `legacy.collections` flag or the old `type: 'content'` property. The new API is more performant, flexible, and future-proof Defining Collections.

What you should do:
Move your `content.config.ts` file from the `components` directory to the root of your `src/` directory (i.e., `src/content.config.ts`). This will allow Astro to properly detect and use your content collections configuration.

const sortedArticles = [...articles].sort((a, b) => {
const dateA = a.data.updated || a.data.created;
const dateB = b.data.updated || b.data.created;
return dateB - dateA;
});