Release Center

Adoption tooling release

Understand a configuration before changing source

Preview preset debt, inspect every workspace project’s activation state, and repair compatibility issues with evidence from the installed package graph.

Current package linev3.5.4

Highlights

Preview

Source-aware preset reports

Run explain-preset —analyze-source to group current lint debt, surface root TypeScript failures first, and preview autofix without writing files.

Review preset adoption

Diagnose

Per-project activation reports

Doctor now explains installed, detected, enabled, and inactive frameworks and feature packs for each workspace project, including TypeScript and Tailwind policy.

Analyze report

Repair

Installed-graph compatibility

Compatibility and Doctor resolve pnpm catalogs, npm aliases, ESM package manifests, companion versions, and Node engine intersections from the actual installation.

Explore CLI diagnostics

Migrate

Safer real-world adoption

Project scoping now covers declaration-only TypeScript packages, shared Astro files, generated Next.js declarations, CLI entry points, and package-local Tailwind CSS graphs.

Configure a monorepo

Upgrade the package

Choose the command for the repository’s package manager:

pnpmnpmYarnBun

bash

pnpm update @santi020k/eslint-config-basic

bash

npm update @santi020k/eslint-config-basic

bash

yarn up @santi020k/eslint-config-basic

bash

bun update @santi020k/eslint-config-basic

After upgrading, run:

pnpmnpmYarnBun

bash

pnpm dlx @santi020k/eslint-config-basic doctor
pnpm dlx @santi020k/eslint-config-basic inspect

bash

npx @santi020k/eslint-config-basic doctor
npx @santi020k/eslint-config-basic inspect

bash

yarn dlx @santi020k/eslint-config-basic doctor
yarn dlx @santi020k/eslint-config-basic inspect

bash

bunx @santi020k/eslint-config-basic doctor
bunx @santi020k/eslint-config-basic inspect

Moving from v1

This release does not change the major-version migration contract. Existing v1 users should follow the v1-to-v2 migration guide and use migrate --write only after reviewing the proposed framework changes.

For package-level release notes, continue to the changelog index.