Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support unoCss #315

Open
oSethoum opened this issue Nov 8, 2023 · 2 comments
Open

support unoCss #315

oSethoum opened this issue Nov 8, 2023 · 2 comments

Comments

@oSethoum
Copy link

oSethoum commented Nov 8, 2023

Hi, please add support for adding unoCss here's the docs https://unocss.dev/integrations/svelte-scoped

@manuel3108 manuel3108 added enhancement New feature or request make a new adder labels Nov 8, 2023
@manuel3108 manuel3108 removed the enhancement New feature or request label May 10, 2024
@bato3
Copy link

bato3 commented May 15, 2024

They have couple integration methods for SK/Svelte https://unocss.dev/integrations/svelte-scoped#when-to-use

Use Case   Description Package to Use
Smaller apps Having 1 global CSS file is more convenient. Use the regular Vite plugin for Svelte/SvelteKit. unocss/vite
Larger apps Svelte Scoped can help you avoid an ever-growing global CSS file. @unocss/svelte-scoped/vite
Component library Generated styles are placed directly in built components without the need to use UnoCSS in a consuming app's build pipeline. @unocss/svelte-scoped/preprocess

@manuel3108
Copy link
Member

I think we should omit the last option for component libraries, svelte-add is designed for apps. As of now I would personally choose the first option, because it's the closest to all other styling adders that we have (bulma, bootstrap, etc.)

But maybe that may change later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants