Closed EliasVal closed 2 months ago
This suggestion worked for me
This suggestion worked for me
While this suggestion didn't exactly work for me, it did lead me to find this, which fixed my issue. Thanks a lot!
Well, I have to re-open the issue since now the plain ESLint CLI disagrees with VSCode and Next.js lint
Why am I also using the ESLint CLI? Monorepo root script
EDIT: I've also tried explicitly setting the tailwindcss.config option in the root .eslintrc.cjs
file
Describe the bug There's a conflict between VSCode/ESlint reporting the error in the editor (Editor reports as OK) and
next lint
(reportstailwindcss/classnames-order
To Reproduce Steps to reproduce the behavior:
tailwindcss/classnames-order
toerror
next lint
to check for errorsExpected behavior Parity between Editor and
next lint
Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
THIS PROJECT IS A MONOREPO!!
Original Line (OK by VSCode):
Suggested fix (By
next lint
)eslint config file or live demo