mirror of
https://github.com/sveltejs/svelte.git
synced 2024-11-25 00:51:01 +01:00
29 lines
1.6 KiB
Markdown
29 lines
1.6 KiB
Markdown
|
---
|
||
|
|
title: Using CSS-in-JS with Svelte
|
||
|
|
description: You don't need to, but you can
|
||
|
|
author: Rich Harris
|
||
|
|
authorURL: https://twitter.com/Rich_Harris
|
||
|
|
---
|
||
|
|
|
||
|
|
CSS is a core part of any web app. By extension, a UI framework that doesn't have a built-in way to add styles to your components is unfinished.
|
||
|
|
|
||
|
|
That's why Svelte allows you to add CSS in a component's `<style>` tag. Co-locating your CSS with your markup means we can [solve the biggest problems developers face when writing CSS](/blog/the-zen-of-just-writing-css) without introducing new ones, all while providing a rather nice development experience.
|
||
|
|
|
||
|
|
But Svelte's style handling does have some limitations. It's too difficult to share styles between components, or apply app-level optimisations. These are areas we plan to address in future versions, but in the meantime if you need those things you can use any framework-agnostic CSS-in-JS library.
|
||
|
|
|
||
|
|
## For example
|
||
|
|
|
||
|
|
Here, we're using [Emotion](https://emotion.sh) to generate scoped class names that can be used across multiple components:
|
||
|
|
|
||
|
|
<div class="max">
|
||
|
|
<iframe
|
||
|
|
title="Aphrodite example"
|
||
|
|
src="/repl/embed?example=blog-svelte-css-in-js"
|
||
|
|
scrolling="no"
|
||
|
|
></iframe>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
It's important to note that most CSS-in-JS libraries have a runtime library, and many don't support statically extracting styles out into a separate <code>.css</code> file at build time (which is essential for the best performance). You should therefore only use CSS-in-JS if it's necessary for your application!
|
||
|
|
|
||
|
|
Note that you can mix-and-match — you can still use Svelte's built-in CSS handling alongside a CSS-in-JS library.
|