Warning source is not identified

[mrleblanc101]

What version of VS Code are you using?

For example: v1.105.1

What version of Tailwind CSS IntelliSense are you using?

For example: v0.14.29

What version of Tailwind CSS are you using?

For example: v4.1.16

What package manager are you using?

For example: npm

What operating system are you using?

For example: macOS

Tailwind CSS Stylesheet (v4) or config file (v3)

Not necessary

VS Code settings

Not necessary

Reproduction URL

A public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.

Not necessary

Describe your issue

This extension should provide a source so people understand where the warning comes from.
I couldn't figure out why running eslint wouldn't return me any error, but I had a yellow underline in the editor.

[KalleDK]

Came here for the same - took me a few takes to realize it was the tailwind plugin

[thecrypticace]

Good call — we'll definitely add this. I'll get a release out later in the week with these. 👍

[mrleblanc101]

@thecrypticace Also, is there an ESLint equivalent to the rules in tailwindcss-intellisense ? I've looking into the source code, and it seem to be custom, and not related to ESLint, so it's annoying because I want my CI to show the same error as my editor.

I know there is an ESLint plugin for Tailwind, but I want to make sure they match ! So a preset would be nice.

[thecrypticace]

There is not — no and we don't have any plans for this currently.

A plugin could technically use the @tailwindcss/language-service package to get diagnostics for source files but its implementation isn't really set up to be usable elsewhere right now (and the setup for it is definitely going to change over the next few months — trying to clean up some code).

[mrleblanc101]

@thecrypticace That's unfortunate, why would I want my editor to lint code ? VS Code only lint the open file, so you can't know if there are errors elsewhere. Also, you can't make pre-commit or CI to block merge if there are errors.

I really think it would be preferable if this was easily sharable with ESLint.
I could use a similar/existing ESLint preset, but there is no way to make sure they always match in their results.