You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have taken the v4 for a spin, and it's very impressive. I have one question/bug report.
The "Done in xms" reported at the end from the TailwindCSS CLI seems to be off by a factor of about 10 compared to the wall time reported by time.
What is this overhead and are there ways to improve this?
time npx tailwindcss -i assets/css/styles.css -o foo.css
≈ tailwindcss v4.0.0-alpha.16
Done in 24ms
npx tailwindcss -i assets/css/styles.css -o foo.css 0.29s user 0.07s system 99% cpu 0.362 total
time ./node_modules/.bin/tailwindcss -i assets/css/styles.css -o foo.css
./node_modules/.bin/tailwindcss -i assets/css/styles.css -o foo.css 0.11s user 0.03s system 97% cpu 0.145 total
Which I guess is in line with the expected overehead of runnind NodeJS.
I have taken the v4 for a spin, and it's very impressive. I have one question/bug report.
time
.The CSS file used as input:
The text was updated successfully, but these errors were encountered: