When generating base without utilities, --tw-transform is missing
See original GitHub issueVersions
Tailwind: v2.2.1 with jit, issue reproducible via CLI Node: 16.10, macOS
Issue
In our project, we have a separate entry point for @tailwind base
(with other custom css reset) and an entry for utilities and components.
When the tailwind run only on the base file, custom properties for transform are not added to :root
.
If I add @tailwind utilities
at the end of this file, it works.
Expected result
The output of @tailwind base
should not depend on the presence of @tailwind utilities
in the file
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Just-in-Time Mode - Tailwind CSS
Generate arbitrary styles without writing custom CSS. ... Since styles are generated on demand, you can just generate a utility for this as...
Read more >Module not found: Can't resolve 'react-native' - Stack Overflow
I'm not sure but in my case it helped to install react native web by npm install react-native-web . Hope it helps you...
Read more >6.3. Preprocessing data — scikit-learn 1.2.0 documentation
The sklearn.preprocessing package provides several common utility functions and transformer classes to change raw feature vectors into a representation that ...
Read more >Transformation Warning: What Does It Mean and What Should ...
Make sure there are no missing transformations. Sometimes, when a transformation can't be found, you can solve it by changing the map's coordinate...
Read more >As utilities risk missing carbon reduction targets, analysts ...
“People at utilities are not climate deniers, but they continue to ... Over the coming years, SEPA's Utility Transformation Challenge will ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey! Tailwind is really meant to process base/components/utilities together, so using separate entry points for each one without combining them with postcss-import or something can have unexpected results. By having the two entries, you are effectively running Tailwind in isolation two separate times — what’s the reason you need to do that?
Just hit this issue too, I assumed I could split parts of tailwind to make better use of caching, Because most of the time, only utilities change for me. It seemed unnecessary to force visitors to redownload entire styling for every simple change.
But if it can’t be effectively split, perhaps there is a way to warn user something is wrong? Otherwise it’s quite obscure issue.