eslint.org Bug: Blog post with misleading (outdated) instructions

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

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

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

I was misdirected into a dead end.

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!

Oct 03 '25 21:10 dwightware4

After checking, I confirmed it was removed in @eslint/css v0.10.0. https://github.com/eslint/css/pull/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.

Oct 04 '25 14:10 kecrily

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

Oct 21 '25 14:10 nzakas

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

Oct 24 '25 08:10 jaymarvelz

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

Oct 24 '25 21:10 dwightware4

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

Oct 27 '25 19:10 dwightware4

@dwightware4 you need to fork the repo and push it to your fork.

Oct 27 '25 21:10 nzakas

👋 Hi! This issue is being addressed in pull request https://github.com/eslint/eslint.org/pull/828. Thanks, @dwightware4!

Oct 27 '25 21:10 eslint-github-bot[bot]