ESLint rules that flag Bootstrap v5 class names, component classes, and data-bs-* attribute values so you can migrate templates toward Bootstrap v6 conventions. Reports are tied to actionable hints; many patterns include an automatic fix.

Upgrading markup across a large codebase is easy to do incompletely. This plugin scans each file’s source (skipping YAML front matter and inline <script> / <style> blocks so those regions are not flagged) and warns where v5-only patterns remain—responsive infix utilities, renamed components, updated form and color utilities, and more.

• ESLint >= 8.57.1 (peer dependency)

The package is not published to npm yet. Install from GitHub (pick your package manager):

npm install --save-dev github:coliff/eslint-plugin-bootstrap-6-migration

pnpm add -D github:coliff/eslint-plugin-bootstrap-6-migration

ESLint resolves the short plugin name bootstrap-migration from the package name eslint-plugin-bootstrap-6-migration.

import bootstrapMigration from "eslint-plugin-bootstrap-6-migration";

export default [
  {
    files: ["**/*.{astro,cjs,html,js,jsx,mjs,tsx,vue}"],
    plugins: {
      "bootstrap-migration": bootstrapMigration,
    },
    rules: {
      "bootstrap-migration/no-v5-classes": "warn",
    },
  },
];

Use "error" instead of "warn" if you want the rule to fail CI.

{
  "plugins": ["bootstrap-migration"],
  "rules": {
    "bootstrap-migration/no-v5-classes": "warn"
  }
}

Point the files / overrides entry at the templates you want checked (HTML, Vue SFCs, JSX, etc.). For raw .html files you may need a plugin such as eslint-plugin-html so ESLint parses those files.

With the ESLint extension installed, problems update as you edit. To run ESLint fixes when you save (for HTML and JS/TS), and to ensure ESLint validates those languages, add the following to your workspace or user settings.json:

{
  "[html][javascript][typescript]": {
    "editor.codeActionsOnSave": {
      "source.fixAll.eslint": "explicit"
    }
  },
  "eslint.validate": ["html", "javascript"]
}

source.fixAll.eslint set to "explicit" runs only when you use Save or Save All (not on every automatic save). Adjust eslint.validate if you use additional file types this plugin checks.

Rule messages reference the same migration hints as in code; auto-fix is applied only when a safe one-to-one replacement is defined.

MIT © Christian Oliff. See LICENSE.