You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
importsatorifrom"satori";// or "satori/wasm"importcreatefrom"satori/tailwind";constsatoriTailwind=create(satori);
hook-like
importsatorifrom"satori";// or "satori/wasm"importhandlerfrom"satori/tailwind";awaitsatori(<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?
The text was updated successfully, but these errors were encountered:
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
hook-like
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?The text was updated successfully, but these errors were encountered: