Update tailwind to ts

[augustuswm]

There is still a type error with the @oxide/design-system import. Looking in node_modules I don't see an exported type file. Do we need a design-system version bump?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
rfd-site	✅ Ready (Inspect)	Visit Preview	Dec 16, 2024 7:04pm

[david-crespo]

Yes, it requires a design-system bump because of oxidecomputer/design-system#97. Unfortunately also bundled in with that release is a change to the color tokens that requires a small but kind of annoying update to the use of Tailwind text color classes everywhere. Example: oxidecomputer/console#2588

I can try to do it, let me see.

[david-crespo]

Oh, it's even worse — @benjaminleonard has to do the whole conversion to the new way asciidoc works. If everything is broken right now I can figure out a workaround that does not require this upgrade.

[augustuswm]

I don't think this has to be done this minute / today. The part stuck here is a fix for the inline GitHub discussions. This is definitely less important than any product work.

[benjaminleonard]

I'm not far off, should have the PR done today or tomorrow.

[benjaminleonard]

Handled in #95 – and we're back up to LTS node.