Skip to content

Astro

Use Astro support from the main v2 package. Application projects no longer install a separate @santi020k/eslint-config-astro package.

bash
pnpm add -D @santi020k/eslint-config-basic

The default install above remains recommended. If you use the manual-dependency lite package, install this framework config package too:

bash
pnpm add -D @santi020k/eslint-config-lite @santi020k/eslint-config-astro eslint
import { defineConfig } from '@santi020k/eslint-config-basic'
export default await defineConfig({
frameworks: {
astro: true
},
typescript: true
})

Most projects can also rely on auto-detection and use eslintConfig() with no framework object.

  • Astro files and embedded script/template linting.
  • Composition through the same @santi020k/eslint-config-basic entry point as every other framework.
  • Compatibility with advanced overrides if you pass a custom config array or factory instead of true.

Enable the optional Astro Doctor ESLint rules for additional performance, accessibility, security, and best-practice diagnostics:

import { defineConfig } from '@santi020k/eslint-config-basic'
export default await defineConfig({
features: {
'astro-doctor': true
},
frameworks: {
astro: true
}
})

This integration adds Astro Doctor’s proprietary ESLint rules without applying the official Astro preset a second time. Health scoring, project audits, baselines, and changed-file scanning remain available through the separate @santi020k/astro-doctor CLI.

  • The internal package still exists in the monorepo for modular development and generated API docs.
  • For the old multi-package installation model, see the v1 Astro guide.

Did this page help?

One click helps us spot documentation that needs another pass. No personal data is sent.