no-legacy-astro-7-experimental-flags

Migrate experimental configuration fields removed or stabilized in Astro 7.

Why

Astro 7 removed the experimental wrappers for advanced routing, caching, logging, route rules, queued rendering, and the Rust compiler. Leaving these fields under experimental can make an upgrade fail validation or silently miss the intended configuration.

Examples

Incorrect

Astro 6 experimental configuration

export default defineConfig({
  experimental: {
    advancedRouting: true,
    cache: { provider: memoryCache() },
    routeRules: {},
    rustCompiler: true,
  },
})

Correct

Astro 7 stable configuration

export default defineConfig({
  cache: { provider: memoryCache() },
  routeRules: {},
})

Configuration

Project audits are configured in doctor.config.ts:

export default {
            rules: {
              'astro-doctor/no-legacy-astro-7-experimental-flags': 'error', // or 'warn' or 'off'
            },
          }

All rules

• astro-doctor/no-client-load-overuse
• astro-doctor/use-astro-image
• astro-doctor/require-image-dimensions
• astro-doctor/no-missing-alt
• astro-doctor/no-set-html
• astro-doctor/no-public-secret-env
• astro-doctor/prefer-class-list
• astro-doctor/no-blocking-script
• astro-doctor/no-unprocessed-script-surprises
• astro-doctor/no-missing-lang
• astro-doctor/require-island-fallback
• astro-doctor/no-process-env
• astro-doctor/prefer-content-collections
• astro-doctor/no-disabled-origin-check
• astro-doctor/no-insecure-session-cookie
• astro-doctor/no-open-allowed-domains
• astro-doctor/no-legacy-astro-7-experimental-flags(this page)
• astro-doctor/prefer-env-schema
• astro-doctor/prefer-pnpm
• astro-doctor/require-action-input-schema
• astro-doctor/require-client-router-script-lifecycle
• astro-doctor/require-content-config
• astro-doctor/require-fetch-default-export