---
{"title": "eslint-plugin-tailwindcss alternatives in 2026", "description": "Several options beside eslint-plugin-tailwindcss: Prettier sorting, editor linting, Stylelint, class merging, and NormWind's shorthand audit.", "url": "https://saydeploy.com/eslint-plugin-tailwindcss-alternatives/", "date": "2026-10-16"}
---
Several options beside eslint-plugin-tailwindcss: Prettier sorting, editor linting, Stylelint, class merging, and NormWind's shorthand audit.

This page compares tools a developer might use in place of eslint-plugin-tailwindcss, an ESLint plugin for Tailwind CSS usage. [^1] The options work at different stages, from formatting and the editor to a CSS linter, class merging, and a command-line audit. Start with the job you need done, then check the Tailwind version and setup in your project.

| Option | What it does | Install or requirements |
|---|---|---|
| prettier-plugin-tailwindcss | Sorts Tailwind classes automatically according to its recommended class order. [^2] | Requires Prettier v3 and is ESM-only. [^2] |
| Tailwind CSS IntelliSense | Autocomplete, syntax highlighting, and linting for Visual Studio Code. [^3] | Requires tailwindcss to be installed to activate. [^3] |
| Stylelint | CSS linter that helps avoid errors and enforce conventions. [^4] | not published |
| tailwind-merge | Merges Tailwind CSS classes in JS without style conflicts. [^5] | Works in all modern browsers and maintained Node versions. [^5] |
| NormWind | Finds Tailwind class pairs that can be written as one shorthand. [^6] | Install from npm as a dev dependency, or run with npx. [^6] |

## Why developers look past eslint-plugin-tailwindcss

Developers look at other tools for a few plain reasons, and each one comes from what eslint-plugin-tailwindcss does and needs. The plugin is made for Tailwind CSS v4 and currently provides 9 rules, with more on the way. [^1] [^1]

Projects still on Tailwind CSS v3 or older ESLint versions can use eslint-plugin-tailwindcss@3.x.x instead. [^1] The plugin also requires a path to its Tailwind CSS configuration, which can be absolute or relative. [^1] [^1]

The plugin is available to everyone for free, and it can be installed as a development dependency (a package used only while building the project) with npm. [^1] [^1] Some readers want a tool that works at another stage, such as formatting code or helping in the editor. A developer comparing tools can check what each one checks, how it reports problems, and where it runs.

## prettier-plugin-tailwindcss: sorts Tailwind classes during formatting

prettier-plugin-tailwindcss is a Prettier v3+ plugin for Tailwind CSS v3.0+ that automatically sorts classes according to its recommended class order. [^2] It runs inside Prettier, the code formatter.

The plugin requires Prettier v3 and is ESM-only, a newer JavaScript module format. [^2] By default it sorts classes in class attributes and in Tailwind @apply directives. [^2]

It can also sort classes on extra attributes, and inside function calls and tagged template literals (a template string with a tag name in front). [^2] [^2] [^2]

## Tailwind CSS IntelliSense: editor help and linting in Visual Studio Code

Tailwind CSS IntelliSense enhances the Tailwind development experience for Visual Studio Code users with autocomplete, syntax highlighting, and linting. [^3] Its linting highlights errors and potential bugs in both CSS and markup. [^3] The extension needs tailwindcss installed before it activates. [^3] For Tailwind CSS v4 and later, activation requires a CSS file that imports a Tailwind CSS stylesheet. [^3]

Hovering over a Tailwind class name shows the complete CSS for that class. [^3]

## Stylelint: a CSS linter for avoiding errors and enforcing conventions

Stylelint is a CSS linter that helps avoid errors and enforce conventions. [^4] It has over one hundred built-in rules for modern CSS syntax and features. [^7] Stylelint can automatically fix problems where possible. [^4]

It can also read CSS-like languages such as SCSS and Less, and it supports plugins for creating custom rules. [^4] [^4] Check whether its built-in rules cover the Tailwind-specific directives your project uses before deciding.

## tailwind-merge: merges Tailwind classes in JS without style conflicts

tailwind-merge is a utility function that merges Tailwind CSS classes in JS without style conflicts. [^5] Its page says it supports Tailwind v4.0 up to v4.3. [^5]

It works in all modern browsers and maintained Node versions, and it has published declarations compatible with TypeScript 3.8 and newer. [^5] [^5] Its job is merging classes, which differs from checking a project for mistakes, so check whether merging is what the project needs. [^5]

## NormWind: finds Tailwind class pairs that can be written as one shorthand

NormWind is made by the team that publishes this site. NormWind says it finds Tailwind class pairs like px-4 py-4 that can be written as one shorthand like p-4. [^6] It flags arbitrary values (custom values written in square brackets) like rounded-[24px] that match a named Tailwind utility like rounded-3xl, using Tailwind's own engine for that match. [^6]

A fix mode rewrites findings in Vue, Svelte, Astro and HTML files, and a wider mode also covers JS, TS, JSX and TSX files. [^6] A preview mode shows which files a fix would change without writing to disk. [^6] Before merging classes, it compares the generated CSS before and after, and skips the merge if they differ. [^6]

It prints output as text, JSON or SARIF 2.1.0, a standard report format that GitHub code scanning reads. It ships as a GitHub Action that annotates pull requests inline. [^6] [^6] It can limit reports to lines changed since a git ref (a named point in the code history such as origin/main). [^6]

The audit exits with code 1 when it finds anything, so it can fail a CI job, meaning the automatic check that runs on each change. [^6] It can also record current findings so that only new ones fail. [^6]

NormWind is free to use, and it is MIT licensed. [^6] [^6] It works with Tailwind CSS v4 projects, and its checks run on Ubuntu, Windows and macOS. [^6] Install it from npm as a dev dependency, or run it once with npx, a command for running npm packages without installing them. [^6]

## How to pick the right eslint-plugin-tailwindcss alternative

Choose prettier-plugin-tailwindcss when the main need is sorting Tailwind classes as part of formatting. [^2] Check that the project uses Prettier v3, which the plugin requires. [^2]

Choose Tailwind CSS IntelliSense when the work happens in Visual Studio Code and editor help is the goal. [^3] Check that tailwindcss is installed in the project, because the extension needs it to activate. [^3]

Choose Stylelint when the checks are about CSS rules, such as avoiding errors and enforcing conventions in stylesheets. [^4] Check whether its built-in rules cover the Tailwind-specific directives your project uses before deciding.

Choose tailwind-merge when the project merges Tailwind classes in JS and needs the result free of style conflicts. [^5] Check that the Tailwind version in use falls within the supported range of v4.0 up to v4.3. [^5]

Choose NormWind when the goal is finding Tailwind class pairs that can become one shorthand, plus arbitrary values that match a named utility, with fixes written back to files and checks that run in CI. [^6] [^6] [^6] Check that the project uses Tailwind CSS v4. [^6]

## Frequently asked questions

### Is eslint-plugin-tailwindcss free to use?

eslint-plugin-tailwindcss is available to everyone for free. [^1] It can be installed as a development dependency with npm. [^1] The required path to the Tailwind CSS configuration can be absolute or relative. [^1] Check that the plugin's setup and the project's Tailwind version fit together before comparing it with an alternative.

### What sorts Tailwind classes during formatting?

prettier-plugin-tailwindcss is a Prettier v3+ plugin for Tailwind CSS v3.0+ that automatically sorts classes according to its recommended class order. [^2] It requires Prettier v3 and is ESM-only. [^2] For Tailwind CSS v4, the plugin needs the CSS file that starts the Tailwind setup to be named in its settings. [^2]

### Which tool gives Tailwind help in Visual Studio Code?

Tailwind CSS IntelliSense enhances the Tailwind development experience for Visual Studio Code users with autocomplete, syntax highlighting, and linting. [^3] It needs tailwindcss installed before it activates. [^3] Its linting highlights errors and potential bugs in both CSS and markup. [^3] Check that the activation file matches the Tailwind version the project uses.

### What merges Tailwind classes without style conflicts?

tailwind-merge merges Tailwind CSS classes without style conflicts. [^5] Its page says it supports Tailwind v4.0 up to v4.3. [^5] It works in all modern browsers and maintained Node versions. [^5] Check that the project's Tailwind version falls inside that range before choosing it.

### Can NormWind fix Tailwind class findings automatically?

NormWind says its fix mode rewrites findings in Vue, Svelte, Astro and HTML files, and a wider mode also covers JS, TS, JSX and TSX files. [^6] A preview mode shows which files a fix would change without writing to disk. [^6] Before merging classes, NormWind compares the generated CSS and skips the merge if the output differs. [^6] Check the file types in your project against that list before running a fix.

NormWind is free with no paid tier. [^6] - [Visit NormWind](/go/start-normwind)

## Sources

[^1]: eslint-plugin-tailwindcss, github.com/francoismassart/eslint-plugin-tailwindcss, read 2026-10-07 (https://github.com/francoismassart/eslint-plugin-tailwindcss)
[^2]: prettier-plugin-tailwindcss, github.com/tailwindlabs/prettier-plugin-tailwindcss, read 2026-10-07 (https://github.com/tailwindlabs/prettier-plugin-tailwindcss)
[^3]: Tailwind CSS IntelliSense, github.com/tailwindlabs/tailwindcss-intellisense, read 2026-10-07 (https://github.com/tailwindlabs/tailwindcss-intellisense)
[^4]: Stylelint, stylelint.io, read 2026-10-09 (https://stylelint.io)
[^5]: tailwind-merge, github.com/dcastil/tailwind-merge, read 2026-10-07 (https://github.com/dcastil/tailwind-merge)
[^6]: NormWind's own description of itself (the product of this site's publisher) (/go/start-normwind)
[^7]: Stylelint, stylelint.io/user-guide/rules, read 2026-10-09 (https://stylelint.io/user-guide/rules/)