JIT compiler avoids compiling all the CSS upfront and compiles only the CSS as and when we need it. This results in lightning-fast build times in all the environments.
So basically it's faster and consumes even less space.
Once one get used to with TailWind, it's awesome!
How "using a strange class that will later be processed to get transformed into a CSS declaration" can be faster that simply "writing the CSS inline with no processing needed" ?
Normally such stuff shouldn't happen and shadows should be configured to be used as
<divclass="shadow-lg"/>
// or with color:
<divclass="shadow-lg shadow-color-name"/>
JIT mode and that ugly class "shadow-[...]" is for rare specific case to do a special shadow just once in one place, and it can be prefixed with hover: to change on hover, it can be prefixed with sm:, md:, lg: classes to be displayed differently on different screen sizes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why instead of doing
We don't simply do
?
What's the benefit of that strange error prone class?
That strange thing is the JIT mode.
As said here,
So basically it's faster and consumes even less space.
Once one get used to with TailWind, it's awesome!
How "using a strange class that will later be processed to get transformed into a CSS declaration" can be faster that simply "writing the CSS inline with no processing needed" ?
Normally such stuff shouldn't happen and shadows should be configured to be used as
JIT mode and that ugly class "shadow-[...]" is for rare specific case to do a special shadow just once in one place, and it can be prefixed with hover: to change on hover, it can be prefixed with sm:, md:, lg: classes to be displayed differently on different screen sizes.