Skip to content
Santi020k ESLint ConfigSanti020k ESLint ConfigESLint Config

Changelog

2.1.1

Section titled “2.1.1”

Patch Changes

Section titled “Patch Changes”

2.1.0

Section titled “2.1.0”

Minor Changes

Section titled “Minor Changes”
  • #93 9bf89ba Thanks @santi020k! - Preserve detected runtime globals when detection infers a preset, including Cloudflare-specific globals, and stop warning for supported typescript.project parser options.

Patch Changes

Section titled “Patch Changes”

2.0.0

Section titled “2.0.0”

Major Changes

Section titled “Major Changes”

  • #87 2ee503b Thanks @santi020k! - Breaking: require ESLint 10. All packages now declare "eslint": "^10.0.0" as peer dependency (previously ^9.0.0 || ^10.0.0), and @santi020k/eslint-config-core depends on @eslint/js v10.

    ESLint v9.x reaches end-of-life on 2026-08-06; targeting v10 only lets the configs rely on v10 behavior:

    • per-file config lookup (eslint.config.* resolved from each linted file’s directory) — workspace packages can now ship their own config files alongside or instead of the root projects option
    • JSX reference tracking — correct scope analysis for JSX without plugin workarounds
    • the updated eslint:recommended baseline from @eslint/js v10

    If you are still on ESLint 9, stay on the v1.x line of these packages.

  • #87 2ee503b Thanks @santi020k! - Lazy framework loading and normalized framework export naming.

    Lazy loading: framework packages (angular-eslint, vue-eslint-parser, eslint-plugin-svelte, …) are now imported dynamically and only when their framework is enabled. Projects that enable none or few frameworks no longer pay the startup cost of loading every bundled framework plugin when eslintConfig() / defineConfig() runs.

    Breaking — normalized naming: framework exports from @santi020k/eslint-config-basic now use bare framework names, and all of them are async factories returning Promise<FlatConfigArray>:

    angular, astro, expo, hono, lit, nest, next, nuxt, qwik, react, reactRouter, slidev, solid, svelte, tanstackStart, vite, vue (plus deprecated remix).

    The previous mixed-style names (angularConfig, expoConfig, nestConfig, nextConfig, reactConfig, solidConfig, svelteConfig, vueConfig) remain available as deprecated aliases of the same factories, but they are no longer plain config arrays — call them (and await the result) when composing manually:

    // before (v1)
    import { reactConfig } from '@santi020k/eslint-config-basic'
    

    export default [...reactConfig]
    // after (v2)
    import { react } from '@santi020k/eslint-config-basic'
    

    export default [...(await react())]

    Most users are unaffected: frameworks: { react: true } and auto-detection behave exactly as before.

    @santi020k/eslint-config-core: the ImportedFramework type now also accepts async factories ((options?) => Promise<FlatConfigArray>), so lazy factories can be passed directly as framework option values.

  • #87 2ee503b Thanks @santi020k! - Release v2 with a single public application install through @santi020k/eslint-config-basic.

    Application projects no longer need to install or import separate framework config packages. Framework integrations are bundled behind the main package and can be enabled with booleans such as frameworks.react: true, frameworks.next: true, or by relying on auto-detection from eslintConfig().

    Detected framework configs are now enabled by default, while an explicit frameworks: {} remains the opt-out path. Next.js, Expo, and Remix automatically include React rules when enabled.

    The documentation site now keeps the previous v1 docs under /v1/, updates the root docs for v2, and includes a v1 to v2 migration guide.

  • #87 2ee503b Thanks @santi020k! - Modernize the React stack and rename Remix:

    • BREAKING: @santi020k/eslint-config-react now uses @eslint-react/eslint-plugin instead of eslint-plugin-react + eslint-plugin-react-hooks. Rule names change from react/* and react-hooks/* to @eslint-react/* (e.g. react-hooks/exhaustive-deps → @eslint-react/exhaustive-deps). This removes the fixupConfigRules compatibility shim, is ESLint 10-native, and includes the hooks rules. react-compiler and react-refresh plugins are unchanged.
    • BREAKING: @santi020k/eslint-config-remix is now a deprecated alias that re-exports @santi020k/eslint-config-react-router (Remix merged into React Router v7). The frameworks.remix key still works but is deprecated — use frameworks['react-router']. The alias will be removed in the next major.
    • The toolchain now builds with TypeScript 6.

Minor Changes

Section titled “Minor Changes”

  • #87 2ee503b Thanks @santi020k! - Add first-class support for Preact.

  • #87 2ee503b Thanks @santi020k! - AI tooling workflow improvements:

    • Default ignores for AI artifacts: the composed config now ignores AI coding-assistant folders (.agent, .agents, .aider*, .claude, .clinerules, .codex, .copilot, .cursor, .gemini, .kiro, .opencode, .roo, .windsurf) so generated agent rules are never linted as source code. Disable via settings: [Setting.NoDefaultIgnores].
    • generate-skill --check: CI mode that compares existing agent skill files (and guarded AGENTS.md / copilot-instructions sections) against freshly generated content without writing, and exits with code 1 when anything is stale or missing.
    • generate-skill --create: scaffolds a root AGENTS.md with the guarded ESLint-standards section when the project has none.
    • doctor duplicate-ESLint detection: warns when the project and the config packages resolve two different ESLint versions (e.g. an ESLint 9 project pulling in the config’s ESLint 10 dependency). Both majors remain supported; the warning helps avoid editor/CLI rule-behavior drift.

  • #87 2ee503b Thanks @santi020k! - Add broader AI tooling support:

    • New agent skill targets in generate-skill: Gemini (.gemini/styleguide.md), Cline (.clinerules/), Roo Code (.roo/rules/), and Kiro (.kiro/steering/ with inclusion: always front-matter). The generator also maintains a guarded ESLint-standards section in an existing root AGENTS.md (the open standard read by Codex CLI, OpenCode, Jules, Amp, and others), mirroring the .github/copilot-instructions.md behavior.
    • New library integrations: Library.Langchain and Library.LlamaIndex add import safety rules for LangChain.js (langchain, @langchain/*) and LlamaIndex.TS (llamaindex, @llamaindex/*) projects, with auto-detection from package.json dependencies.
    • Generated agent skills now report AI SDK, MCP, Mastra, OpenAI Agents, LangChain, and LlamaIndex integrations in the feature summary.

  • dfba51d Thanks @santi020k! - Improve config migration handling and enhance TypeScript options detection

  • #87 2ee503b Thanks @santi020k! - Add optional ignores to eslintConfig() / EslintConfigOptions for extra global ignore globs, documented in the configuration guide.

  • #87 2ee503b Thanks @santi020k! - Add defineConfig as a named alias for eslintConfig, keep implicit framework expansion from mutating caller-provided options, declare ESLint as a peer dependency of the umbrella package, and mark the package as side-effect free for bundlers.

  • #87 2ee503b Thanks @santi020k! - Fix optionMergeStrategy: 'merge' so explicitly passed options (tools, testing, formats, libraries, extensions, frameworks) are actually unioned with detected and preset values, as documented. Previously, providing any of these options silently replaced detected/preset values regardless of strategy. To fully opt out of detected frameworks, use autoFrameworks: false or optionMergeStrategy: 'replace' (an explicit frameworks: {} no longer opts out under the default merge strategy).

    Other fixes:

    • detection: false now also disables the default detected extensions (Unicorn, Perfectionist, Security); a new granular detection: { extensions: false } control is available.
    • Negated glob patterns (!pattern) in projects sub-configs are now scoped correctly instead of producing invalid path/!glob patterns.
    • Deprecate the unused TsOptions interface (typescript: { project } was ignored since v2) and correct stale doc comments on ImportedFramework and the no-op Setting.Gitignore / Setting.DefaultIgnores values.

  • #87 2ee503b Thanks @santi020k! - Disable context-sensitive framework rules that produce false positives in lint-staged and monorepo layouts: Nest’s provider reference rule and Next’s Pages Router link rule.

  • #91 59158db Thanks @santi020k! - Tailwind noUnknownClasses option, expanded testing config names, and virtual TS parser fix.

    • TailwindOptions.noUnknownClasses: new optional field ('error' | 'warn' | 'off' | false) to control the better-tailwindcss/no-unknown-classes rule severity. Defaults to 'error' when a Tailwind entry point is detected; set to false or 'off' to disable.
    • Testing config overrides: TESTING_CONFIG_NAMES now maps Cypress, Jest, JestDom, Playwright, TestingLibrary, and Vitest — so per-testing-tool file overrides are applied for all supported testing integrations, not just Playwright.
    • TypeScript virtual file parser: the parser-setup config block now also covers virtual TS files (parserSetupFiles includes GLOB_VIRTUAL_TS), fixing missing parser options for framework-generated virtual modules.

  • #87 2ee503b Thanks @santi020k! - Add new framework and integration support:

    • New framework packages: Nuxt (@nuxt/eslint-plugin on top of the Vue config), Lit (eslint-plugin-lit + eslint-plugin-wc), React Router v7 (successor to Remix), and TanStack Start (bundles TanStack Router + Query rules). All are wired into eslintConfig() framework keys, bundled resolvers, auto-detection (nuxt, lit, @react-router/dev, @tanstack/react-start, @tanstack/solid-start), the CLI, and the agent-skill generator.
    • New formats: Format.Css (official @eslint/css plugin) and Format.Html (@html-eslint).
    • New extensions: Extension.Node (eslint-plugin-n, with TS-aware module-resolution overrides), Extension.Compat (browserslist compatibility), Extension.DeMorgan, Extension.Depend, and Extension.Oxlint (disables rules covered by Oxlint for hybrid setups, applied last like Biome).
    • New tool: Tool.Pnpm (eslint-plugin-pnpm) enforcing pnpm catalogs and workspace settings in package.json and pnpm-workspace.yaml.

Patch Changes

Section titled “Patch Changes”

2.0.0-beta.3

Section titled “2.0.0-beta.3”

Patch Changes

Section titled “Patch Changes”

2.0.0-beta.2

Section titled “2.0.0-beta.2”

Minor Changes

Section titled “Minor Changes”

  • Tailwind noUnknownClasses option, expanded testing config names, and virtual TS parser fix.

    • TailwindOptions.noUnknownClasses: new optional field ('error' | 'warn' | 'off' | false) to control the better-tailwindcss/no-unknown-classes rule severity. Defaults to 'error' when a Tailwind entry point is detected; set to false or 'off' to disable.
    • Testing config overrides: TESTING_CONFIG_NAMES now maps Cypress, Jest, JestDom, Playwright, TestingLibrary, and Vitest — so per-testing-tool file overrides are applied for all supported testing integrations, not just Playwright.
    • TypeScript virtual file parser: the parser-setup config block now also covers virtual TS files (parserSetupFiles includes GLOB_VIRTUAL_TS), fixing missing parser options for framework-generated virtual modules.

Patch Changes

Section titled “Patch Changes”

2.0.0-beta.1

Section titled “2.0.0-beta.1”

Minor Changes

Section titled “Minor Changes”
  • dfba51d Thanks @santi020k! - Improve config migration handling and enhance TypeScript options detection

Patch Changes

Section titled “Patch Changes”

2.0.0-beta.0

Section titled “2.0.0-beta.0”

Major Changes

Section titled “Major Changes”

  • #87 2ee503b Thanks @santi020k! - Breaking: require ESLint 10. All packages now declare "eslint": "^10.0.0" as peer dependency (previously ^9.0.0 || ^10.0.0), and @santi020k/eslint-config-core depends on @eslint/js v10.

    ESLint v9.x reaches end-of-life on 2026-08-06; targeting v10 only lets the configs rely on v10 behavior:

    • per-file config lookup (eslint.config.* resolved from each linted file’s directory) — workspace packages can now ship their own config files alongside or instead of the root projects option
    • JSX reference tracking — correct scope analysis for JSX without plugin workarounds
    • the updated eslint:recommended baseline from @eslint/js v10

    If you are still on ESLint 9, stay on the v1.x line of these packages.

  • #87 2ee503b Thanks @santi020k! - Lazy framework loading and normalized framework export naming.

    Lazy loading: framework packages (angular-eslint, vue-eslint-parser, eslint-plugin-svelte, …) are now imported dynamically and only when their framework is enabled. Projects that enable none or few frameworks no longer pay the startup cost of loading every bundled framework plugin when eslintConfig() / defineConfig() runs.

    Breaking — normalized naming: framework exports from @santi020k/eslint-config-basic now use bare framework names, and all of them are async factories returning Promise<FlatConfigArray>:

    angular, astro, expo, hono, lit, nest, next, nuxt, qwik, react, reactRouter, slidev, solid, svelte, tanstackStart, vite, vue (plus deprecated remix).

    The previous mixed-style names (angularConfig, expoConfig, nestConfig, nextConfig, reactConfig, solidConfig, svelteConfig, vueConfig) remain available as deprecated aliases of the same factories, but they are no longer plain config arrays — call them (and await the result) when composing manually:

    // before (v1)
    import { reactConfig } from '@santi020k/eslint-config-basic'
    

    export default [...reactConfig]
    // after (v2)
    import { react } from '@santi020k/eslint-config-basic'
    

    export default [...(await react())]

    Most users are unaffected: frameworks: { react: true } and auto-detection behave exactly as before.

    @santi020k/eslint-config-core: the ImportedFramework type now also accepts async factories ((options?) => Promise<FlatConfigArray>), so lazy factories can be passed directly as framework option values.

  • #87 2ee503b Thanks @santi020k! - Release v2 with a single public application install through @santi020k/eslint-config-basic.

    Application projects no longer need to install or import separate framework config packages. Framework integrations are bundled behind the main package and can be enabled with booleans such as frameworks.react: true, frameworks.next: true, or by relying on auto-detection from eslintConfig().

    Detected framework configs are now enabled by default, while an explicit frameworks: {} remains the opt-out path. Next.js, Expo, and Remix automatically include React rules when enabled.

    The documentation site now keeps the previous v1 docs under /v1/, updates the root docs for v2, and includes a v1 to v2 migration guide.

  • #87 2ee503b Thanks @santi020k! - Modernize the React stack and rename Remix:

    • BREAKING: @santi020k/eslint-config-react now uses @eslint-react/eslint-plugin instead of eslint-plugin-react + eslint-plugin-react-hooks. Rule names change from react/* and react-hooks/* to @eslint-react/* (e.g. react-hooks/exhaustive-deps → @eslint-react/exhaustive-deps). This removes the fixupConfigRules compatibility shim, is ESLint 10-native, and includes the hooks rules. react-compiler and react-refresh plugins are unchanged.
    • BREAKING: @santi020k/eslint-config-remix is now a deprecated alias that re-exports @santi020k/eslint-config-react-router (Remix merged into React Router v7). The frameworks.remix key still works but is deprecated — use frameworks['react-router']. The alias will be removed in the next major.
    • The toolchain now builds with TypeScript 6.

Minor Changes

Section titled “Minor Changes”

  • #87 2ee503b Thanks @santi020k! - Add first-class support for Preact.

  • #87 2ee503b Thanks @santi020k! - AI tooling workflow improvements:

    • Default ignores for AI artifacts: the composed config now ignores AI coding-assistant folders (.agent, .agents, .aider*, .claude, .clinerules, .codex, .copilot, .cursor, .gemini, .kiro, .opencode, .roo, .windsurf) so generated agent rules are never linted as source code. Disable via settings: [Setting.NoDefaultIgnores].
    • generate-skill --check: CI mode that compares existing agent skill files (and guarded AGENTS.md / copilot-instructions sections) against freshly generated content without writing, and exits with code 1 when anything is stale or missing.
    • generate-skill --create: scaffolds a root AGENTS.md with the guarded ESLint-standards section when the project has none.
    • doctor duplicate-ESLint detection: warns when the project and the config packages resolve two different ESLint versions (e.g. an ESLint 9 project pulling in the config’s ESLint 10 dependency). Both majors remain supported; the warning helps avoid editor/CLI rule-behavior drift.

  • #87 2ee503b Thanks @santi020k! - Add broader AI tooling support:

    • New agent skill targets in generate-skill: Gemini (.gemini/styleguide.md), Cline (.clinerules/), Roo Code (.roo/rules/), and Kiro (.kiro/steering/ with inclusion: always front-matter). The generator also maintains a guarded ESLint-standards section in an existing root AGENTS.md (the open standard read by Codex CLI, OpenCode, Jules, Amp, and others), mirroring the .github/copilot-instructions.md behavior.
    • New library integrations: Library.Langchain and Library.LlamaIndex add import safety rules for LangChain.js (langchain, @langchain/*) and LlamaIndex.TS (llamaindex, @llamaindex/*) projects, with auto-detection from package.json dependencies.
    • Generated agent skills now report AI SDK, MCP, Mastra, OpenAI Agents, LangChain, and LlamaIndex integrations in the feature summary.

  • #87 2ee503b Thanks @santi020k! - Add optional ignores to eslintConfig() / EslintConfigOptions for extra global ignore globs, documented in the configuration guide.

  • #87 2ee503b Thanks @santi020k! - Add defineConfig as a named alias for eslintConfig, keep implicit framework expansion from mutating caller-provided options, declare ESLint as a peer dependency of the umbrella package, and mark the package as side-effect free for bundlers.

  • #87 2ee503b Thanks @santi020k! - Fix optionMergeStrategy: 'merge' so explicitly passed options (tools, testing, formats, libraries, extensions, frameworks) are actually unioned with detected and preset values, as documented. Previously, providing any of these options silently replaced detected/preset values regardless of strategy. To fully opt out of detected frameworks, use autoFrameworks: false or optionMergeStrategy: 'replace' (an explicit frameworks: {} no longer opts out under the default merge strategy).

    Other fixes:

    • detection: false now also disables the default detected extensions (Unicorn, Perfectionist, Security); a new granular detection: { extensions: false } control is available.
    • Negated glob patterns (!pattern) in projects sub-configs are now scoped correctly instead of producing invalid path/!glob patterns.
    • Deprecate the unused TsOptions interface (typescript: { project } was ignored since v2) and correct stale doc comments on ImportedFramework and the no-op Setting.Gitignore / Setting.DefaultIgnores values.

  • #87 2ee503b Thanks @santi020k! - Disable context-sensitive framework rules that produce false positives in lint-staged and monorepo layouts: Nest’s provider reference rule and Next’s Pages Router link rule.

  • #87 2ee503b Thanks @santi020k! - Add new framework and integration support:

    • New framework packages: Nuxt (@nuxt/eslint-plugin on top of the Vue config), Lit (eslint-plugin-lit + eslint-plugin-wc), React Router v7 (successor to Remix), and TanStack Start (bundles TanStack Router + Query rules). All are wired into eslintConfig() framework keys, bundled resolvers, auto-detection (nuxt, lit, @react-router/dev, @tanstack/react-start, @tanstack/solid-start), the CLI, and the agent-skill generator.
    • New formats: Format.Css (official @eslint/css plugin) and Format.Html (@html-eslint).
    • New extensions: Extension.Node (eslint-plugin-n, with TS-aware module-resolution overrides), Extension.Compat (browserslist compatibility), Extension.DeMorgan, Extension.Depend, and Extension.Oxlint (disables rules covered by Oxlint for hybrid setups, applied last like Biome).
    • New tool: Tool.Pnpm (eslint-plugin-pnpm) enforcing pnpm catalogs and workspace settings in package.json and pnpm-workspace.yaml.

Patch Changes

Section titled “Patch Changes”

1.6.0

Section titled “1.6.0”

Minor Changes

Section titled “Minor Changes”

  • #85 664693e Thanks @santi020k! - Add basic-eslint generate-skill CLI command and generateAgentSkills() API.

    The new command scans a project for AI coding-assistant agent folders (.agent, .agents, .claude, .cursor, .windsurf, .copilot, .aider) and writes a tailored ESLint standards skill file into each one. The generated file describes the active configuration (TypeScript, frameworks, testing, tools, etc.) and instructs the agent to follow the project’s lint conventions automatically.

    A companion GitHub Actions workflow (.github/workflows/agent-skills.yml) is included so projects can auto-regenerate skill files whenever the ESLint config changes.

    Usage:

    Terminal window
    npx basic-eslint generate-skill          # write skill files (skip existing)
    npx basic-eslint generate-skill --force  # overwrite all skill files

    Programmatic API:

    import { generateAgentSkills } from '@santi020k/eslint-config-basic'
    

    const { skipped, written } = generateAgentSkills({
      cwd: process.cwd(),
      force: true
    })

Patch Changes

Section titled “Patch Changes”

  • #85 664693e Thanks @santi020k! - Load optional integrations lazily so projects can import the base config without installing unrelated integration peers such as Storybook, GraphQL, Stencil, Cypress, or Testing Library.

    Also include the generated agent-skill API entry in the basic package build output so published packages do not reference a missing agent-skill-generator.js file.

  • Updated dependencies [664693e]:

1.5.0

Section titled “1.5.0”

Minor Changes

Section titled “Minor Changes”
  • #82 af844f6 Thanks @santi020k! - - Add first-class Hono support with Worker runtime globals, package detection, and a playground for Cloudflare Workers-style projects.
    • Lower the Node.js engine requirement to >=22.18.0 in package.json and .nvmrc, and validate CI against Node.js 22.
    • Update README.md with a landing pointer to the canonical docs site.

Patch Changes

Section titled “Patch Changes”

1.4.0

Section titled “1.4.0”

Minor Changes

Section titled “Minor Changes”

  • #80 7bccef0 Thanks @santi020k! - # v1.4.0 — API improvements, new optional, and quality-of-life fixes

    Breaking changes

    Section titled “Breaking changes”

    Unified Node.js requirement to >=24.0.0. All packages in the monorepo now strictly require Node.js 24.0.0 or higher. This ensures compatibility with modern dependency versions (such as cspell v10) and aligns with the project’s long-term maintenance strategy.

    detectProjectOptions() no longer sets boolean flags on frameworks. Previously, auto-detection would set frameworks.react = true, frameworks.next = true, etc. Passing those values to eslintConfig() would throw a TypeError because framework configs must be real imports, not booleans.

    Detected frameworks are now reported via a new detectedFrameworks: DetectedFrameworkName[] field. The frameworks object in the detection result stays empty, so spreading detectProjectOptions() into eslintConfig() is always safe.

    // Before (would throw)
    const opts = detectProjectOptions()
    

    eslintConfig(opts) // ❌
    

    // opts.frameworks.next === true → TypeError inside eslintConfig()
    

    // After (safe)
    const opts = detectProjectOptions()
    

    // opts.detectedFrameworks → ['next', 'react']  (informational)
    // opts.frameworks → {}                          (safe to spread)
    eslintConfig(opts) // ✅

    New features

    Section titled “New features”

    Extension.BestPractices optional config — adds four quality rules with no extra dependencies:

    • no-console (warn) — catches leftover debug output
    • no-alert (error) — disallows browser alert / confirm / prompt
    • complexity (warn, max 10) — flags overly complex functions
    • max-depth (warn, max 4) — flags deeply nested blocks
    eslintConfig({ extensions: [Extension.BestPractices] })

    Category barrel exports for @santi020k/eslint-config-optionals — five new sub-path exports let you import a whole category at once:

    // also: /extensions  /tools  /libraries

    NextMode auto-detection — detectProjectOptions() now detects App Router vs Pages Router by checking for an app/ or src/app/ directory, so options.nextMode is set automatically.

    DetectedFrameworkName type — new exported union type listing all framework names that detectProjectOptions() can detect. Useful for display logic or tooling built on top of detection.

    Improvements

    Section titled “Improvements”

    Early tsconfigRootDir validation — createTypescriptConfig() now throws a clear, actionable error at config-creation time if the provided tsconfigRootDir path does not exist on disk, instead of failing silently at ESLint runtime.

    CI node version matrix — the build pipeline now runs against Node 24.x to ensure stability across the updated engine requirements.

    docs/PHILOSOPHY.md — new document explaining the major design decisions: why hard deps, flat config only, lazy framework loading, rule severity philosophy, and how to extend or override rules.

    Changelog synchronization — new sync-docs-changelog.mjs script to automatically propagate root changelog updates to the documentation site.

    Bug Fixes

    Section titled “Bug Fixes”
    • CLI Scaffolding: Resolved bug where auto-detected frameworks were not correctly included in the generated configuration.
    • Rule Set Update: Updated React and Expo collections to reflect rule removals in eslint-plugin-react-hooks@7 recommended configuration.
    • Tailwind CSS Performance: Fixed Atomics.wait() timeout errors in monorepos by providing customizable settings in the recommended Tailwind configuration.

    Dependency Updates

    Section titled “Dependency Updates”
    • External Plugins:
      • Updated @cspell/eslint-plugin to v10.0.0 (Major).
      • Updated typescript-eslint to v8.59.0.
      • Updated eslint-plugin-react-hooks to v7.1.1.
      • Updated eslint-plugin-perfectionist to v5.9.0.
      • Updated eslint-plugin-sonarjs to v4.0.3.
      • Updated tailwindcss to v4.2.4.
    • Core Tooling:
      • Updated eslint to v10.2.1.
      • Updated vitest and @vitest/coverage-v8 to v4.1.5.
      • Internal alignment of typescript version to v5.9.3.

Patch Changes

Section titled “Patch Changes”

1.3.0

Section titled “1.3.0”

Minor Changes

Section titled “Minor Changes”
  • #77 450fa19 Thanks @santi020k! - Refresh package metadata and supporting docs for the santi020k.com domain migration.
    • Update documentation, canonical URLs, and package links from santi020k.me to santi020k.com.
    • Sync npm package metadata so published packages point to the correct license, repository, issues page, and documentation URLs.
    • Refresh low-risk ESLint ecosystem and release tooling dependencies.

Patch Changes

Section titled “Patch Changes”

1.2.0

Section titled “1.2.0”

Minor Changes

Section titled “Minor Changes”

  • #74 c63e902 Thanks @santi020k! - # v1.2.0 Release - Documentation Overhaul

    This release focuses on a comprehensive update of the documentation site and branding refresh.

    Highlights

    Section titled “Highlights”
    • VitePress Refresh: Major updates to the documentation structure, including new guides and improved navigation.
    • Branding Assets: Added new official logos, icons, and social preview images (opengraph) in packages/docs/public.
    • Theme Enhancements: Custom styling and component improvements for a more premium documentation experience.
    • Improved Installation Guide: Updated steps for getting started with the latest features.

Patch Changes

Section titled “Patch Changes”

1.1.0

Section titled “1.1.0”

Minor Changes

Section titled “Minor Changes”

  • #70 ef658c1 Thanks @santi020k! - # 1.1.0 Release

    Update Highlights

    Section titled “Update Highlights”
    • ESLint 10 Support: Harmonized ESLint version to ^10.1.0 across the monorepo and playgrounds.
    • Security Patches: Fixed vulnerabilities in lodash, esbuild, and path-to-regexp via root overrides.
    • Solid Playground Fix: Resolved MODULE_NOT_FOUND error in the Solid playground linting process.

Patch Changes

Section titled “Patch Changes”

1.0.0

Section titled “1.0.0”

Minor Changes

Section titled “Minor Changes”

  • #66 6f2f473 Thanks @santi020k! - v0.10.0 Release

    Major Changes

    Section titled “Major Changes”
    • Migration to pnpm: Full migration of the monorepo from npm to pnpm workspaces (pnpm v10+). This includes better performance, stricter dependency management, and corepack integration.
    • neostandard removal: Removed neostandard dependency to provide more granular control and modularity in core rules.
    • Stylistic v4 -> v5: Upgraded to @stylistic/eslint-plugin version 5.x for improved formatting rules and TypeScript 5.7+ support.
    • GraphQL Integration: Added comprehensive support for GraphQL schemas and operations. This includes automated project detection for GraphQL files and specialized linting rules for both schema definitions and operation documents.
    • React 19 Support: Updated React detection logic and configurations to support React 19.

    Framework Updates

    Section titled “Framework Updates”
    • Qwik & Remix Support: Added comprehensive ESLint configurations and functional playground environments for both Qwik and Remix frameworks.
    • Dependency Alignment: Resolved critical typescript-eslint dependency issues in Astro, Svelte, and Vue packages to ensure proper rule resolution and type safety.
    • Consistency Refinements: Standardized disable-type-checked rule blocks across all framework-specific configurations.
    • Documentation Overhaul: Major documentation refresh in root README.md and VitePress documentation. Added clarity on configuration priority, framework auto-detection, and full-settings examples.

    Maintenance

    Section titled “Maintenance”
    • Corepack Enablement: Added corepack support for automated package manager version management.
    • Turbo Update: Bumped Turborepo to v2.9+ for faster builds and improved task caching.
    • Turbo Optimizations: Configured Turborepo to output in errors-only mode with errorsOnlyShowHash enabled, significantly reducing terminal noise during build and lint tasks.
    • Integration Test Improvements: Enhanced integration tests to be more robust, including proper tsconfigRootDir handling and better React version validation.
    • Playground Synchronization: Updated all playground packages to maintain parity with the latest framework rules.

  • #55 d8e4b4a Thanks @santi020k! - feat: add standard ESLint configuration and resolve typecheck/hook failures

    This release introduces a new standard configuration in @santi020k/eslint-config-core and addresses several technical issues:

    • Fixed global typecheck failures across the monorepo.
    • Resolved pre-commit hook issues with cspell.
    • Fixed pre-push hook failures related to publint in the playground package.
    • Added missing test coverage scripts and fixed CI build failures.

Patch Changes

Section titled “Patch Changes”

0.8.1

Section titled “0.8.1”

Minor Changes

Section titled “Minor Changes”
  • 13e8e5a: # Release 0.8.0
    • Snippet Fixes: Resolved ESLint parsing errors in virtual TypeScript files within Markdown, Astro, and VitePress code blocks by disabling type-aware rules for those snippets.
    • Standalone TS Support: Restored disableTypeChecked configuration in the TypeScript package, ensuring it remains fully functional and parsing-error-free when used without the main composer.
    • Documentation Reorganization: Significantly expanded and restructured the documentation site, adding new pages for the Inspector, CLI Tooling, Extensions, and better framework-specific guides.
    • Branding Update: Updated the author link label from “Website” to “Author” across all documentation files for improved brand identity.
    • Composition Improvements: Refactored the configuration composer to be more robust when handling virtual snippets and framework contracts.

Patch Changes

Section titled “Patch Changes”

  • CI & Workflow Stabilization

    • Fixed invalid actions/setup-node version from @v6 to @v4 in Release and Docs workflows.
    • Improved CLI test performance and reliability by refactoring integration tests into fast in-memory unit tests.
    • Enabled Turborepo caching in GitHub Actions to significantly reduce PR build times.

  • Updated dependencies

  • Updated dependencies [13e8e5a]

    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1
    • @santi020k/eslint-config-…@0.8.1

0.7.1

Section titled “0.7.1”

Patch Changes

Section titled “Patch Changes”

0.7.0

Section titled “0.7.0”

Minor Changes

Section titled “Minor Changes”

Patch Changes

Section titled “Patch Changes”

0.6.0

Section titled “0.6.0”

Minor Changes

Section titled “Minor Changes”
  • #39 1c11dec Thanks @santi020k! - feat(astro): add robust defaults and virtual script support for Astro 5+ feat(core): standardize internal dependencies to workspace:* for better monorepo development docs: add Tailwind CSS v4 compatibility notes and workarounds to README

Patch Changes

Section titled “Patch Changes”

0.5.0

Section titled “0.5.0”

Minor Changes

Section titled “Minor Changes”
  • #36 85d6a5e Thanks @santi020k! - feat(astro): add robust defaults and virtual script support for Astro 5+ feat(core): standardize internal dependencies to workspace:* for better monorepo development docs: add Tailwind CSS v4 compatibility notes and workarounds to README

Patch Changes

Section titled “Patch Changes”

0.4.0

Section titled “0.4.0”

Minor Changes

Section titled “Minor Changes”
  • #34 f015876 Thanks @santi020k! - feat: add eslint-plugin-sonarjs as optional config chore: remove tailwindcss from playground and test package dependencies docs: update AI Agent skills in README

Patch Changes

Section titled “Patch Changes”

0.3.0

Section titled “0.3.0”

Minor Changes

Section titled “Minor Changes”
  • #28 162afdb Thanks @santi020k! - feat: add regexp optional config with eslint-plugin-regexp
    • New OptionalOption.Regexp to enable regex linting via eslint-plugin-regexp
    • Catches common regex mistakes: exponential backtracking, unnecessary escapes, and optimizable character classes
    • Uses recommended rules with selective overrides for smoother adoption

Patch Changes

Section titled “Patch Changes”

  • #27 577abbe Thanks @santi020k! - ci: disable Husky git hooks during the release workflow

    • Added HUSKY=0 environment variable to the release workflow to prevent Git hooks from interfering with the automated release process

  • #25 1fb4693 Thanks @santi020k! - feat: add GitHub-linked changelogs and automatic GitHub releases with tags

    • Switched changelog generator to @changesets/changelog-github for richer changelogs with PR links, commit references, and contributor credits
    • Configured release workflow to create GitHub releases with git tags on publish

  • Updated dependencies [162afdb, 1fb4693]:

0.2.0

Section titled “0.2.0”

Minor Changes

Section titled “Minor Changes”
  • feat: add Nest.js, Vue, and Expo ESLint configs with optionals package
    • Added @santi020k/eslint-config-nest with NestJS-specific linting rules
    • Added @santi020k/eslint-config-vue with Vue 3 linting rules
    • Added @santi020k/eslint-config-expo with Expo/React Native linting rules
    • Added @santi020k/eslint-config-optionals for optional integrations (Tailwind, Vitest, cspell, i18next, MDX, Markdown, Stencil)
    • Added ConfigOption.Nest, ConfigOption.Vue, and ConfigOption.Expo enum values
    • Updated PR template with changeset reminder

Patch Changes

Section titled “Patch Changes”

0.1.0

Section titled “0.1.0”

Minor Changes

Section titled “Minor Changes”
  • publish testing

Patch Changes

Section titled “Patch Changes”

Did this page help?

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