eslint-plugin-tailwindcss-vite-sfc-issue

While developing, eslint throws 'tailwindcss/no-custom-classname' warnings/errors, even if the custom classes are defined in the Vue SFC.

The problem goes away after a 'vite build'. It seems, that the dist/ directory plays an important role here. In vite dev mode, no dist/ directory is created - instead everything goes directly to the browser.

Check with 'npm run lint'.

Top categories

Loading Svelte Themes