@ParasBansal10
Keep in mind, that it uses runtime tailwind-merge dependency, which makes which somewhat impacts the performance. Great Video Kyle.
@AbhishekSingh-e2t1k
In a production environment, the screen size for users will be fixed, meaning end users won't see the animation. Therefore, I believe this feature may not be necessary.
@shazyzone
This is awesome, thanks!
@rawux
Thanks for this!
@jenstornell
The missing Tailwind feature. Thanks!
@tegathemenace
A big mistake I made as a frontend dev is tryna make it so fluid. Knowing fully well I'm the only person resizing it this much. I just stick to good ole rem and change the base units for the 4 main device viewports. If you want to view the blog article whilst frantically resizing the page that's between you and your psychiatrist.😂
@abbashali01
But why does it need to animate between breakpoints. Its not like the real user is gonna change his screen size continuously. Or am i missing something
@praveenkumars3375
Nicee... something like combination of vh and vw unit.
@ä½ çš„æš±ç¨±
You can achieve the same behavior with clamp().
@shisui2575
I feel like you could just use the view width, and wrap it in a clamp
@atisozols
I am having trouble setting this up
@kasper369
Isn't useless, when is using going to resize screen anyway
@curefilms
Why can't we use clamp? Instead
@tandomrandom
Yes my users always plays with viewport to piss me off 😂😂😂 do not do this. It just bloats and slowdown your app
@saudalghamdi5608
Is this the equivalent to "clamp" CSS property?
@TavenScents
But who s able switch his device instantly while staying in the same page in order to notice this.
@jsonkody
thats so good it will probably be added to plain TW no?
@mariomario4676
awesome
@sanusihassan7125
I don't know why would someone want to do that?
@madsxcva