-
**What's happening**
This [documentation](https://craco.js.org/recipes/use-linaria/) for [Linaria](https://github.com/callstack/linaria?tab=readme-ov-file#setup) is outdated. The proposed plugin [cra…
-
Is it possible to get SCSS pre-processing to work with Linaria within Next? It seems like it could work but I couldn't get it to work. Should it? It seems like it could given the right Webpack conf…
-
It would be great to see this project support a linaria target. Especially after the release of RSC and the app directory in next.js 🙂
-
Linaria uses wyw-in-js as its engine. It would be interesting to see an example of its usage. It has plugins for Webpack; can we use them with compatibility? Currently, the new version of MUI (v6) use…
-
-
Hey there,
Using Linaria and the code below:
```ts
import { css } from '@linaria/core';
import { createVar } from 'css-variable';
const myColor = createVar({ value: 'rebeccapurple' });
e…
-
## Packages:
- wyw-in-js version: **0.5.1**
- Bundler: **vite@5.2.8**
- **@linaria/react@6.1.0**
## Description
There is an issue with simple `styled` interpolation upon vite build.
![imag…
-
I am using using Subj. for a few mounts now. Tailwind provides theme and utility classes while Linaria is used to define components and compose Tailwind design tokens and classes.
In nextjs next-wi…
-
Related to #61232
## Goal
- [ ] Replace Emotion with another technology to author styles
- [ ] Build-time compilation (ie. no runtime compilation)
- [ ] Keep classname obfuscation
## Context
The `…
-
## Describe the enhancement
Supply the ability to declare aliases for `css` and `styled` when running `stylelint` analysis for projects that export those methods from `linaria` with a different nam…