Hugo Pipes and Tailwind’s upcoming Oxide engine

[bwintx]

An upcoming version of Tailwind CSS will use a Rust-based “Oxide” engine that, among other things, incorporates PostCSS rather than requiring it as a separate dependency. Has anyone had a chance to test whether Hugo Pipes will still be able to use resources.PostCSS to work with Tailwind/Oxide?

References:

• https://youtu.be/CLkxRnRQtDE?t=2146 (start of the Oxide-related portion of Adam Wathan’s mid-2023 talk about upcoming Tailwind features)
• https://www.pushpaje.com/blog/introducing-tailwind-css-oxide

[bep]

@bwintx

incorporates PostCSS rather than requiring it as a separate dependency.

As I understand it from other sources, they will start using lightningcss instead of PostCSS, but oI may be wrong. In any case,

• Tailwind will still be a program that Hugo can interact with.
• I doubt it will work out of the box (since resources.PostCSS works with … PostCSS directly)
• I’m also pretty sure it will be a simple fix in Hugo to get it working.
• Also, I’m a Tailwind user, so it will likely have a high priority …

[bwintx]

Thanks. It definitely will include Lightning CSS but it’s unclear as yet whether it truly dumps PostCSS or simply embeds it somehow. Anyway, am very glad to know you’ll be addressing it when the time comes!

Edit: Found this, FWIW:
https://nitter.net/jullerino/status/1733417261879132193