I've tried to add the eslint-plugin-tailwindcss config object to the eslint.config.js in multiple ways ... There is the same problem with my program,but i can't fix it. ... Sign up to request clarification or add additional context in comments. ... Yeah...after some more testing I concluded that the plugin is simply not compatible with svelte.

March 15, 2024 - Is your feature request related to a problem? Please describe. TailwindCSS 4 is in alpha and will be released soon. Currently I cannot use this module with Tailwind 4 because package.json specifies ^3.4.0. Describe the solution you'd lik...

July 16, 2025 - fix: enforces-shorthand does not work for h- & w- when prefixed (by Kamahl19 🙏) ... feat: support tailwind config in typescript (by quesabe 🙏) You may have to upgrade your Tailwind CSS version to 3.3.2 ... Use .eslintrc.* file to configure ...

June 18, 2024 - Fixing these issues was straightforward. I simply ran yarn lint --fix, and the tool automatically corrected most of the problems. I first came across eslint-plugin-tailwindcss while trying to fix bugs in the shad/cn open source project.

August 28, 2023 - Extension can not resolve config from eslint settings (tailwindcss settings property) while using cli execute this plugin in correct way. What should you do to see this issue: Extend some variable to tailwind theme, for example primary-1...

francoismassart / eslint-plugin-tailwindcss Public · There was an error while loading. Please reload this page. Notifications · You must be signed in to change notification settings · Fork 110 · Star 2k · Search Issues · is:issue state:open · is:issue state:open Search · LabelsMilestonesNew issue · Open · Closed · bugSomething isn't workingSomething isn't working ·

3 weeks ago - For ESLint, you can install the VSCode ESLint plugin and configure it to automatically fix the classes on save by adding the following options to your .vscode/settings.json: { // enable VSCode to fix tailwind classes on save "editor.codeActionsOnSave": { "source.fixAll.eslint": "explicit" } }

Is it normally with this? And is there any possible way to find the wrong TailwindCSS className on VSCode editor or CLI prompt? I heard eslint-plugin-tailwindcss only supports TailwindCSS v3, not v4.

Supporters Talk about the plugin on your social networks ... feat: support tailwind config in typescript (by quesabe 🙏) You may have to upgrade your Tailwind CSS version to 3.3.2 ... Use .eslintrc.* file to configure rules in ESLint < v9.

February 8, 2024 - "devDependencies": { "@types/node": "^20", "@types/react": "^18", "@types/react-dom": "^18", "@typescript-eslint/eslint-plugin": "^5.49.0", "@typescript-eslint/parser": "^5.49.0", "autoprefixer": "^10.0.1", "eslint": "^8", "eslint-config-airbnb": "^19.0.4", "eslint-config-airbnb-typescript": "^17.0.0", "eslint-config-next": "14.1.0", "eslint-config-prettier": "^8.10.0", "eslint-config-standard-with-typescript": "^34.0.0", "eslint-formatter-codeframe": "^7.32.1", "eslint-import-resolver-typescript": "^3.5.3", "eslint-plugin-import": "^2.27.5", "eslint-plugin-n": "^15.6.1", "eslint-plugin-prettier": "^5.1.3", "eslint-plugin-promise": "^6.1.1", "eslint-plugin-react": "^7.32.2", "eslint-plugin-unused-imports": "^2.0.0", "husky": "^8.0.0", "postcss": "^8", "prettier": "^3.2.4", "prettier-plugin-tailwindcss": "^0.5.11", "tailwindcss": "^3.3.0", "typescript": "^5" }

April 25, 2024 - Is your feature request related to a problem? Please describe. I'm using nuxt and the latest @nuxt/eslint module which utilizes eslint version 9 and I couldn't make it work. If I import the eslint-plugin-tailwindcss index file in the new...

March 30, 2025 - The plugin configuration is defined inside the .eslintrc file. This is why adding the custom class name to the safelist didn’t work in my case. However, the class is preserved in the final CSS bundle. Since this is a linting issue, no-custom-classname allows whitelisting any custom class inside the .eslintrc file: module.exports = { // ... overrides: [ // ... { rules: { 'tailwindcss/no-custom-classname': [ 'warn', { whitelist: ['code-annotation'] } ] } } ] };

This version has been made possible thanks to the work of hyoban and his project tailwind-api-utils. ... There was an error while loading. Please reload this page. ... There was an error while loading. Please reload this page. ... This patch release is the same as v3.8.0, I had to publish patch versions in the regular npm release channel in order to update the README. Here is a copy of the important message as added in the README: While the development of eslint-plugin-tailwindcss for Tailwind CSS v4 is ongoing, you can use the latest version published on the beta channel to get partial support of Tailwind CSS v4.

July 13, 2022 - Here we're extending the recommended rule sets from ESLint, Prettier, and the Tailwind CSS plugin, as well as specifying eslint-plugin-tailwindcss itself to be used as a plugin. We're also setting some defaults for our project environment and parser options. NOTE: This is the most basic setup.

July 2, 2025 - // @ts-check import tailwindcss from '@poupe/eslint-plugin-tailwindcss'; export default [ { files: ['**/*.css'], language: 'css/css', // Required plugins: { tailwindcss, }, rules: { 'tailwindcss/valid-theme-function': 'error', 'tailwindcss/valid-modifier-syntax': 'error', 'tailwindcss/valid-apply-directive': 'error', 'tailwindcss/no-arbitrary-value-overuse': 'warn', 'tailwindcss/prefer-theme-tokens': 'warn', 'tailwindcss/no-conflicting-utilities': 'error', }, }, ];

This plugin works out of the box with most popular tailwind utilities: ... In case an utility is not supported or you have built your own, you can change which literals will get linted for each rule. Read the API documentation to learn how to override or extend the default config. All rules are intended to automatically fix the tailwind classes. If you have installed the VSCode ESLint plugin, you can configure it to automatically fix the classes on save by adding the following options to your .vscode/settings.json:

May 31, 2021 - Describe the bug Custom TW classes are being underlined. To Reproduce Steps to reproduce the behavior: On 1.14.3 extend Tailwind colors Error still shown Expected behavior It should recognize the classes from the tailwind.config.js Scree...