Closed pintariching closed 1 year ago
Ok I added a --watch
flag to the CLI and I can proudly say it's faster than Tailwind both on the initial run and on subsequent runs. I still have to publish proper benchmarks but from my testing, parsing the background_color
input.html
file takes tailwind
around 300 ms on the first run and railwind
around 15 ms. On subsequent runs without changing anything, tailwind
does become faster and drops down to around 20 ms, while railwind
time stays the same.
If anybody wants to play around and create benchmarks that would be awesome!
A cool feature is tailwinds
--watch
(I think that's the flag?), to continously watch the file or directory and automaticaly recompile on changes.