Oxide as WASM Module?

[bjesuiter]

Hi there,

could this oxide engine be compiled as wasm to make it usable in edge environments, like deno deploy?

I Experiment heavily with the whole deno ecosystem and especially their web framework, deno fresh, and I like it very much.
One difference from node is the fully runtime/buildless workflow of most things in deno.

They currently use twind as a runtime based tailwind clone in the "Fresh" framework, which is not optimal, bc. It misses certain tailwind features and needs to be kept up-to-date regularly with the upstream tailwind repo.

[adamwathan]

Yeah this is something I expect we will be digging into in the near future since we'll need it to properly deploy the oxide engine to play.tailwindcss.com 👍

[bjesuiter]

Nice to hear that! If you have anything like a PR or something to test, I'd be interested in beta testing :)

[jlukic]

Very curious on this. Was trying to reverse engineer how play.tailwindcss.com is generating class names, looks like a brotli and lightningcss wasm file are being used.

Any chance you can share what your workaround has been so far?

Also curious on the package @tailwindcss/oxide-wasm32-wasi it appears to have a browser wasm, but haven't been able to get it to work (seeing some errors related to SharedArrayBuffer transfer from wasm related to threading).

[jlukic]

I've gone ahead and submitted a PR for browser wasm support #18292