Tailwindcss takes a long time to compile

[marvinhagemeister]

Mostly making this issue as a note for me to investigate a bit. Looked at the tailwind internals a while back here https://marvinh.dev/blog/speeding-up-javascript-ecosystem-part-8/ . So there is lots of room to speed it up.

We might also speed the UX up greatly by adding proper HMR support.

[king8fisher]

Wondering if transitioning to UnoCSS could give us better results?
https://unocss.dev/integrations/runtime mentions something that might be appealing to Fresh.
Might need a migration guide.

[marvinhagemeister]

I benchmarked all the various libraries when writing the article. UnoCSS takes the same time as tailwindcss. We need to create styles also server side.

[miguelrk]

Although fresh sort-of went the tailwindcss route already, it would be cool to (officially) have unocss as an alternative as well, by landing #1966 which I've been using (unofficialy) already for a while and should be ready 👍🏼

[marvinhagemeister]

@miguelrk Who's going to maintain the UnoCSS plugin? If we merge it than the burden falls on me.

[miguelrk]

Good point, totally understandable @marvinhagemeister... in case it helps someone, I maintain a fork 👍🏼 . In any case, eager to see improvements in the HMR space!

[marvinhagemeister]

Closing, as I've been sporadically in touch with the tailwindcss team and they made great strides in improving compilation performance. Once their new major version is out I'd expect it to be noticeably faster.