require-client-router-script-lifecycle

Why it matters

ClientRouter navigation swaps page content without reloading the document, so DOMContentLoaded only initializes the first page. Astro emits astro:page-load after the initial load and every client-side navigation.

See the difference

<script>
  document.addEventListener('DOMContentLoaded', initialize)
</script>

<script>
  document.addEventListener('astro:page-load', initialize)
</script>

Configure this check

Project audits are configured in doctor.config.ts:

export default {
  rules: {
    'astro-doctor/require-client-router-script-lifecycle': 'error',
  },
}

Use 'error', 'warn', or 'off'. The configuration guide covers presets and per-file overrides.

Keep exploring best practices

• prefer-class-listUse class:list directive for conditional or dynamic class names.
• no-process-envDisallow process.env in Astro files — use import.meta.env instead.
• prefer-content-collectionsPrefer Content Collections over Astro.glob() or import.meta.glob() for Markdown and MDX files.
• no-legacy-astro-7-experimental-flagsMigrate experimental configuration fields removed or stabilized in Astro 7.
• prefer-env-schemaDefine an Astro env schema for variables documented in .env.example.
• prefer-pnpmUse pnpm consistently and remove competing package-manager lockfiles.
• require-content-configAdd a content config when src/content contains entries.
• require-fetch-default-exportRequire a default export from Astro 7 advanced-routing entrypoints.

Browse every rule and project audit