This is one of the Netflix pages
Compared with the class name (.checkbox) that uses a specific name, using tailwind requires adding a lot of class names (e.g. mr-1, mt-2). After many people maintain, the strings in the class name will become many.
I think this will be difficult to maintain and read. Someone has the similar experience using tailwind. How do you solve it?
TailwindCSS allows you to still add custom CSS files while using their syntax using directives. You can read about it here.
https://tailwindcss.com/docs/functions-and-directives
Instead of having to write inline code everywhere like
<div class="p-4 m-4 flex-row">
You can create directives that you can use the same as regular classes.
#tailwind base;
#tailwind components;
#tailwind utilities;
#layer components {
.row {
#apply p-4 m-4 flex-row;
}
}
Which then allows you to write less class names
<div class="row">
Related
This question already has an answer here:
Passing a string as a prop and using it to make a class name in Svelte
(1 answer)
Closed 22 days ago.
I've got a <div> which is toggling between translate classes like so:
<div class={`w-96 fixed top-16 bottom-0 left-0 transition-transform -translate-x-${show ? '0' : '96'}`}>
And Tailwind is just not applying this style, and I don't understand why. The class is added to the element, but not the styling.
The styling for all the other classes is added, except for -translate-x-96.
This is my app.css:
#tailwind base;
#tailwind components;
#tailwind utilities;
Tailwind v3 generates styles for classes it finds by scanning the files specified in content field in tailwind.config.js. This means that the classes should be present in the code as-is and should not be constructed by concatenation.
From https://tailwindcss.com/docs/content-configuration#class-detection-in-depth:
The way Tailwind scans your source code for classes is intentionally very simple — we don’t actually parse or execute any of your code in the language it’s written in, we just use regular expressions to extract every string that could possibly be a class name.
The fix in this case is to specify the full class name in both branches of the ternary operator:
`${show ? '-translate-x-0' : '-translate-x-96'}`
I am picking up a project that was left unfinished and used semantic-ui-react for some menu components. I decided to add tailwindcss to make my life easier when styling but I'm running into a rather weird issue.
When I include these lines at the top of my main CSS file, tailwindcss works and I can style normal HTML tags perfectly fine
#tailwind base;
#tailwind components;
#tailwind utilities;
However, something goes wrong under the hood because a semantic-ui menu that was previously styled like this
Is now styled like this
It's specifically the #tailwind base; line that is the breaking change. So I can toggle between my webpage looking like pic 1 and 2 by adding and removing that line.
People don't usually use tailwind and semantic-ui together so I couldn't find anything on the internet about this. Hoping someone will know what could be going on.
My goal is to be able to use tailwindcss to add styling to components just like normal, without random overrides of default semantic-ui styling.
I'm learning tailwindcss recently，and I don't understand the #tailwind screens;
Offical Doc
Who can explain it or show the usage ？
In the previous release of Tailwind (v2), #tailwind screens; would generate responsive utility classes at build-time.
However, in Tailwind v3, this has been replaced by the more generic directive #tailwind variants;.
I found it in the offical repository test file.
#tailwind screens; is just a anchor where the #media style generated will be injected rather than very end of stylesheet.
#tailwind screens; is deprecated since tailwindcss v2.2 certainly. I found the changelog.
I want to make my navbar responsive by adding hidden sm:flex to a specific item. Meaning it'll hidden by default but show only on small screens and above. I made some debug and discover that hidden override everything even the responsive variants. Other display properties work will on responsive variants. here's my code:
className="hidden sm:flex sm:w-2/5 w-11/12 mt-4 sm:mt-0 items-center shadow-md"
Tailwind is driven by mobile first design, just like bootstrap and some other CSS frameworks. Reference: https://tailwindcss.com/docs/responsive-design/#mobile-first
That means that classes without variants will be applied to smaller screens first, and then you can add variants for bigger screens.
So, the thing that you want to achieve should be like this:
className="flex md:hidden w-2/5 md:w-11/12 mt-0 md:mt-4 items-center shadow-md"
I hope this helps!
I got the same error in a rails application. The issue was that I was importing tailwind base styles twice. Check the code below.
#import "tailwindcss/base";
#import "tailwindcss/components";
#import "tailwindcss/utilities";
#import "tailwindcss/screens";
#tailwind base;
#tailwind components;
#tailwind utilities;
#tailwind screens;
To fix make sure you only import them once like this:
#import "tailwindcss/base";
#import "tailwindcss/components";
#import "tailwindcss/utilities";
#import "tailwindcss/screens";
Hope this fixes your issue.
Might be probably too late but for someone looking for an answer the solution is to remove
#tailwind screens;
In my case, the guide I followed only advised me to import the following:
#tailwind base;
#tailwind components;
#tailwind utilities;
The solution for me was simple. I added the following import:
#tailwind screens;
Background: svelte^3.0.0 with tailwind^3.0.24
I am trying to import a library of CSS classes into the responsive directive.
Animate.css contains a bunch of classes and keyframe animations from https://daneden.github.io/animate.css/
The error I get back is:
🚫 CssSyntaxError: #apply cannot be used with .fadeInRight because .fadeInRight either cannot be found, or its actual definition includes a pseudo-selector like :hover, :active, etc. If you're sure that .fadeInRight exists, make sure that any #import statements are being properly processed before Tailwind CSS sees your CSS, as #apply can only be used for classes in the same CSS tree.
The end goal is to render a different animation depending on the screen size in a tailwind way.
i.e.
<div className="animated tw-fadeInBottom md:tw-fadeInRight faster"></div>
The css file being built by tailwind looks something like this.
#import '../assets/css/Animate.css';
#tailwind base;
#tailwind components;
#tailwind utilities;
#responsive {
.tw-fadeIn {
#apply fadeIn
}
}
For new users coming here, I have made a simple port of Animate.css that is compatible with TailwindCSS-style animations, and hence can be directly used by the #apply,etc. directives.
Link for docs: https://github.com/ikcb/animated-tailwindcss#readme
Basic Usage
To install, run:
npm i -D animated-tailwindcss
# or
yarn add -D animated-tailwindcss
Then just wrap your config with withAnimations (and remove import of Animate.css from CSS):
const withAnimations = require('animated-tailwindcss');
module.exports = withAnimations({
// ... your config here ...
});
Other alternatives: I was able to find out a plugin tailwindcss-animatecss that does more or less the same thing except for long configuration. But it was available when this question was asked. Strangely no one pointed it out.
Now regarding the error you were getting, any class that is used by directives but is neither a part of TW core, nor injected by some plugin/configuration, must be defined under a #layer directive.
So one actually needs to do something like this (if not preferring to use any third-party package):
#tailwind base;
#tailwind components;
#tailwind utilities;
#layer utilities {
// define your Animate.css classes here
}
// use them here or in your code