Optional TailwindCSS

[flamrdevs]

Feature Request

Optional TailwindCSS

Description

satori has built-in TailwindCSS (experimental) support, but should this be a built-in feature? not all developers prefer to use TailwindCSS.

Example API overview

wrapper-like

import satori from "satori"; // or "satori/wasm"
import create from "satori/tailwind";

const satoriTailwind = create(satori);

hook-like

import satori from "satori"; // or "satori/wasm"
import handler from "satori/tailwind";

await satori(<Component />, {
	classHandle: handler
});

This make satori more framework-agnostic, more performant and smaller bundle-size (especially for edge-runtime,worker,deno).
Then if TailwindCSS is still a built-in feature, why doesn't satori support UnoCSS(attributify,variant-group) or even MasterCSS?