Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Tailwind Support

See original GitHub issue

I am not sure if this is something, which fits well into Emmet, but I think it does. Did you ever consider Emmet support for Tailwind classes? Many Tailwind classes are short by default, but there are still possible abbreviations, which would be helpful. Examples:

tb => text-base
fb => font-bold
tc500 => text-cyan-500
ic => items-center

Thoughts?

Thanks!

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

sergechecommented, Dec 9, 2021

Emmet produces structured output dynamically: it takes basically any word and produces tags from it. That’s why it limits itself to specific code places where it can be activated: you wouldn’t expect HTML tags white typing HTML attribute name or attribute value, right?

What I see from Tailwind docs is that it’s just a bunch of predefined utility classes. There’s nothing dynamic about it and they are tied specifically to class="..." attribute value (where Emmet shouldn’t work by design since it’s used to produce HTML markup).

Your case is exactly what editors’ text snippets should be used for: in editors like Sublime Text or VSCode you can create a list of static snippets what should work inside class="..." and provide nice completions popup

0reactions

sprankhubcommented, Dec 8, 2021

Okay, can you elaborate why you think this is not a good addition to Emmet itself?