Aman Mittal • 3/30/2025

Resolving invalid custom Tailwind classname ESLint warning

Read Original

This article explains a common issue where custom CSS class names (like 'code-annotation') trigger Tailwind CSS ESLint warnings. It details why adding the class to Tailwind's safelist doesn't resolve the linting error and provides the correct solution: whitelisting the custom class within the eslint-plugin-tailwindcss configuration in the .eslintrc file.

0 comments
#Frontend #eslint #css
Resolving invalid custom Tailwind classname ESLint warning

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes