Legacy flags

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 until you are able to fully update your project code.

collectionsBackwardsCompat

Type: boolean
Default: false

追加： astro@6.0.0

Provides temporary backwards compatibility for projects unable to migrate to the Content Layer API introduced in v5.0.

astro.config.mjs

import { defineConfig } from "astro/config";

export default defineConfig({
  legacy: {
    collectionsBackwardsCompat: true,
  },
});

When enabled, this preserves the following legacy v4 content collections features:

• 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. Migrate collections to the Content Layer API, then disable this flag.