near
🔷 [Epic] Build step support (i.e. TailwindCSS)
Some popular tools like TailwindCSS require a build step. Maybe the build could be performed in a smart contract prior to chain save
Setting as medium impact because developers really love Tailwind and we will get a lot of requests for it. It is also a really good match for quick component development
according to this tweet, Tailwind may be shipping their new engine written in Rust by EOY. Hopefully we can leverage that as WASM
Tailwind Rust solution is based on LightningCSS: https://x.com/adamwathan/status/1649391725272604672
came across a better intro to Tailwind's new Oxide engine, scroll down to Next, I gave a sneak peek at Oxide, the next evolution of the Tailwind CSS engine. on this post
https://tailwindcss.com/blog/2023-07-18-tailwind-connect-2023-recap
most importantly, take some time to watch the linked section of the keynote, Tailwind is on the verge of some major tooling changes which not only could allow us to run it in the browser since it is written in Rust but also handles some other CSS complexities we may encounter
If we don't use it as our primary CSS tooling, we can leverage LightningCSS directly in the browser
https://lightningcss.dev/docs.html#from-deno-or-in-browser
@andy-haynes @calebjacob
Update from Tailwind 3.4 release announcement
If you’ve been paying close attention, you might be wondering about Oxide, the engine improvements we previewed at Tailwind Connect this summer.
We’d originally slated those improvements for v3.4, but we have a few things still to iron out and so many of these other improvements had been piling up that we felt it made sense to get it all out the door instead of holding it back. The Oxide stuff is still coming, and will be the headlining improvement for the next Tailwind CSS release in the new year.
https://tailwindcss.com/blog/tailwindcss-v3-4