Folders and files
| Name | Name | Last commit date | ||
|---|---|---|---|---|
Zero-runtime CSS in JS library.
- Write CSS in JS, but with zero runtime, CSS is extracted to CSS files during build
- Familiar CSS syntax with Sass like nesting
- Use dynamic prop based styles with the React bindings, uses CSS variables behind the scenes
- Easily find where the style was defined with CSS sourcemaps
- Lint your CSS in JS with stylelint
- Use JavaScript for logic, no CSS preprocessor needed
- Optionally use any CSS preprocessor such as Sass or PostCSS
- Supports atomic styles with @linaria/atomic
Learn how Airbnb improved both developer experience and web performance with Linaria
npm install @linaria/core @linaria/react @wyw-in-js/babel-presetor
yarn add @linaria/core @linaria/react @wyw-in-js/babel-presetLinaria is now built on top of wyw-in-js.dev. It supports various bundlers to extract the CSS at build time. To configure your bundler, check the following guides on the wyw-in-js.dev site:
See Configuration to customize how Linaria processes your files.
Linaria relies on WyW (@wyw-in-js/*) to evaluate your modules at build time and extract CSS. If you hit issues like slow builds, invalidation storms, or unexpected code being executed during the build, it’s usually related to the WyW evaluation model and how your modules are structured.
Linaria 8 requires Node.js >=22.12.0 (aligned with the WyW 2 / Oxc dependency graph). WyW 2 defaults to eval.strategy: "hybrid", so statically provable values are resolved before falling back to the evaluator for dynamic values.
If your build depends on evaluator-only side effects or exact CSS rule order ties, review the Linaria 8 migration notes in docs/MIGRATION_GUIDE.md.
See https://wyw-in-js.dev/stability for practical guidance and common pitfalls.
Linaria can be used with any framework, with additional helpers for React. The basic syntax looks like this:
import { css } from '@linaria/core';
import { modularScale, hiDPI } from 'polished';
import fonts from './fonts';
// Write your styles in `css` tag
const header = css`
text-transform: uppercase;
font-family: ${fonts.heading};
font-size: ${modularScale(2)};
${hiDPI(1.5)} {
font-size: ${modularScale(2.5)};
}
`;
// Then use it as a class name
<h1 className={header}>Hello world</h1>;You can use imported variables and functions for logic inside the CSS code. They will be evaluated at build time.
If you're using React, you can use the styled helper, which makes it easy to write React components with dynamic styles with a styled-component like syntax:
import { styled } from '@linaria/react';
import { families, sizes } from './fonts';
// Write your styles in `styled` tag
const Title = styled.h1`
font-family: ${families.serif};
`;
const Container = styled.div`
font-size: ${sizes.medium}px;
color: ${props => props.color};
border: 1px solid red;
&:hover {
border-color: blue;
}
${Title} {
margin-bottom: 24px;
}
`;
// Then use the resulting component
<Container color="#333">
<Title>Hello world</Title>
</Container>;Dynamic styles will be applied using CSS custom properties (aka CSS variables) and don't require any runtime.
See Basics for a detailed information about the syntax.
- Basics
- API and usage
- Configuration
- Dynamic styles with css tag
- Theming
- Critical CSS extraction
- Bundlers integration
- CLI
- Linting
- How it works
- Example
We appreciate any support in library development!
Take a look on Contributing docs to check how you can run Linaria in development mode.
-
No IE11 support when using dynamic styles in components with styled, since it uses CSS custom properties
-
Dynamic styles are not supported with css tag. See Dynamic styles with css tag for alternative approaches.
-
Modules used in the CSS rules cannot have side-effects. For example:
import { css } from '@linaria/core'; import colors from './colors'; const title = css` color: ${colors.text}; `;
Here, there should be no side-effects in the colors.js file, or any file it imports. We recommend to move helpers and shared configuration to files without any side-effects.
Linaria can work together with other CSS-in-JS libraries out-of-the-box. However, if you want to use styled components from Linaria as selectors in styled-components/emotion, you need to use @linaria/interop
- Syntax Highlighting - language-babel
- Autocompletion - vscode-styled-components
- Linting - stylelint
- Syntax Highlighting and Autocompletion - language-babel
- Syntax Highlighting & Autocompletion - webstorm-styled-components
- Syntax Highlighting & Autocompletion - Naomi, JSCustom (refer to document on how to turn on Styled Component syntax)
- Linting - SublimeLinter-stylelint, LSP Stylelint
- gatsby-plugin-linaria – Gatsby plugin that sets up Babel and webpack configuration for Linaria.
- polished.js - A lightweight toolset for writing styles in JavaScript.
- craco-linaria - A Craco plugin that allows you to use Linaria without ejecting from a CRA.
This project wouldn't have been possible without the following libraries or the people behind them.
Special thanks to @kentcdodds for his babel plugin and @threepointone for his suggestions and encouragement.
Linaria is an open source project and will always remain free to use. If you think it's cool, please star it 🌟. Callstack is a group of React and React Native geeks, contact us at hello@callstack.com if you need any help with these or just want to say hi!
Like the project? ⚛️ Join the team who does amazing stuff for clients and drives React Native Open Source! 🔥
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!