Bug: Blog post with misleading (outdated) instructions

[dwightware4]

URL(s)

https://eslint.org/blog/2025/02/eslint-css-support/

What did you do?

I followed the instructions in the blog post, but it sent me on a bit of a wild goose chase.

What did you expect to happen?

I expected the instructions to at least point me in the correct direction.

What actually happened?

I was misdirected into a dead end.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

This blog post instructs users to try to import tailwindSyntax from @eslint/css/syntax which no longer exists.

The correct instructions can be found in the README in the eslint/css repo.

The blog post shows up first in Google results, and sent me on a bit of a wild-goose-chase, so hopefully you guys can update it for future folks.

Thanks so much!

[kecrily]

After checking, I confirmed it was removed in @eslint/css v0.10.0. eslint/css#166

I recommend keeping the original content and adding code examples for versions after v0.10.0. Mark this as accepted, and feel free to submit a PR.

[nzakas]

@dwightware4 are you interested in submitting a pull request for this?

[jaymarvelz]

@nzakas Since there hasn’t been a response for a while, would you like me to take this on?

[dwightware4]

@nzakas yes I can submit a PR for this. I'll get it in next week.

[dwightware4]

@nzakas I have the PR ready but I don't have permission to push my branch.