Resolving invalid custom Tailwind classname ESLint warning
Read OriginalThis 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.
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
No top articles yet