Joshua Nelson
Joshua Nelson
## Describe the enhancement I think it'd be useful if it were possible to generate more readable class names in development, for example: ```ts import { css } from '@linaria/atomic';...
## Describe the enhancement Currently, atomic styles produces an object in the resulting code like this: ```ts const atoms = css` background: red; width: 100%; `; // gets compiled to...
## Describe the enhancement To correctly merge together atomic styles, we should expand shorthand properties. https://github.com/johanholmerin/style9/blob/10d282d17732a15409fcdc59ba75ed152f219e3f/docs/Usage-guide.md#shorthands contains some info on how this can work. We just need to explode properties...
## Describe the enhancement I've run into some issues using `@linaria/extractor` with `@linaria/atomic`, where when evaluating dependencies, it tries to evaluate `@linaria/atomic` which includes calls to `fs` (which we don't...
- Operating System: All - Node Version: v12 - NPM Version: v7 - webpack Version: 4 / 5 - mini-css-extract-plugin Version: Suggested to be 1.5.0 ### Feature Proposal I would...
We've noticed a discrepancy in how preact / react server renders a component that looks like this: ``` import React from "preact/compat"; import "./styles.css"; export default function App() { return...
Breaks for things such as https://github.com/yahoo/react-intl
How does this scale? What is the overhead of introducing new trees? It'd be good to include some sort of performance test for this too.
If you're running React 18, but using the legacy API's still, _reactRootContainer is undefined, but it doesn't have the _internalRoot property on it. This should fix that – in React...