DEV Community


Discussion on: Moving From Tailwind To Vanilla-er CSS

terabytetiger profile image
Tyler V. (he/him)

Preflight - this is completely optional, just don't include the directive for it

While this is true, I don't think it's particularly relevant to the author's point - which is that when you follow the Installation page's instructions, you end up with fully reset styles and it can be jarring to new users.

Javascript dependencies - If you want to avoid adding TW to your build chain, simply use the official CLI tool which lets you build on the fly without touching the rest of your code base.

The first line of the installation page which discusses this option is:

For simple projects or just giving Tailwind a spin [...]

and under the "Using Tailwind via CDN" section there's this statement:

To get the most out of Tailwind, you really should install it as a PostCSS plugin.

Everything the author has run into that you're calling out is from following the recommended installation guide in the Tailwind docs and will align with the experience of many new users.

owenmelbz profile image
Owen Melbourne

Not really interested in any excuses tbf - The fact of the matter is sharing false information.

If people with less experience read that - they will repeat and take it for truth.

If a balanced argument is provided, they will be educated with both sides.