Skip to content
Santi020k ESLint ConfigSanti020k ESLint ConfigESLint Config
You are viewing the v1 archive. For current setup guidance, use the v3 docs; the v2 release is preserved at /v2/.

CLI

The main package ships a CLI that can scaffold or refresh the project config.

pnpm
pnpm dlx @santi020k/eslint-config-basic init
pnpm dlx @santi020k/eslint-config-basic update
npm
npx @santi020k/eslint-config-basic init
npx @santi020k/eslint-config-basic update
yarn
yarn dlx @santi020k/eslint-config-basic init
yarn dlx @santi020k/eslint-config-basic update
bun
bunx @santi020k/eslint-config-basic init
bunx @santi020k/eslint-config-basic update
bunx @santi020k/eslint-config-basic generate-skill

What It Does

Section titled “What It Does”
  • Detects TypeScript, runtime, and supported optional integrations from package.json.
  • Chooses eslint.config.js for ESM projects.
  • Chooses eslint.config.mjs otherwise.
  • Includes explicit framework imports in generated configs.
  • Adds React automatically when Next.js or Expo is detected.

Usage

Section titled “Usage”
pnpm
pnpm dlx @santi020k/eslint-config-basic init
npm
npx @santi020k/eslint-config-basic init
yarn
yarn dlx @santi020k/eslint-config-basic init
bun
bunx @santi020k/eslint-config-basic init

If the package is already installed locally, the basic-eslint bin is also available through your package manager’s local binary resolution.

Update an Existing Config

Section titled “Update an Existing Config”
pnpm
pnpm dlx @santi020k/eslint-config-basic update
npm
npx @santi020k/eslint-config-basic update
yarn
yarn dlx @santi020k/eslint-config-basic update
bun
bunx @santi020k/eslint-config-basic update

Use update when you want to regenerate the file after adding or removing dependencies.

Generate Agent Standards (Beta)

Section titled “Generate Agent Standards (Beta)”

The generate-skill command creates or updates ESLint standards files for AI coding assistants (Cursor, Claude, Copilot, etc.) based on your project’s active configuration.

This is a beta feature and is non-breaking (it only adds/updates files in .agent, .cursor, .claude, etc. folders).

pnpm
pnpm dlx @santi020k/eslint-config-basic generate-skill
npm
npx @santi020k/eslint-config-basic generate-skill
yarn
yarn dlx @santi020k/eslint-config-basic generate-skill
bun
bunx @santi020k/eslint-config-basic generate-skill

Use --force if you want to overwrite existing standards files.

When to Use Each Command

Section titled “When to Use Each Command”
  • Use init when the project does not have an ESLint flat config yet.
  • Use update when the dependency graph changed and you want a fresh generated baseline.
  • Use manual editing when the config already has custom organization that you do not want regenerated.

Why the Generated Config Stays Explicit

Section titled “Why the Generated Config Stays Explicit”

The CLI is the bridge between detection and maintainable source code. Detection can infer that a project uses Next.js or Astro, but the generated file still writes explicit imports so your config remains readable and reviewable.

Notes

Section titled “Notes”
  • The CLI detects frameworks, but it does not hide them behind implicit runtime magic.
  • Existing eslint.config.js or eslint.config.mjs files are respected for updates.
  • The generated file is a starting point that you can still edit by hand.
Section titled “Repository Links”
Section titled “Related Pages”

Did this page help?

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