Devon Govett
Devon Govett
You need to run Tailwind's transformer before passing valid (standard) CSS to Lightning CSS.
This is intentional. It is needed to handle the opposite case, like these ones: #774 #311. Say CSS adds a new selector to the standard. The goal of a tool...
These closing tags are optional according to the HTML specification. https://html.spec.whatwg.org/multipage/syntax.html#optional-tags
lol why would anyone input a string like that in reality?
You can add it to your `babel.config.json` already right?
Hmm I don't think so. Babel will run in addition to the default transpiler. You can configure babel to only include the react compiler and not include things like preset-env,...
React Compiler will increase the bundle size a bit due to the extra code it generates for memoization, so I don't think that's unexpected.
Looks like this would lose support for brace expansion: https://github.com/micromatch/picomatch?tab=readme-ov-file#library-comparisons so I guess it would be a breaking change.
`@property` is only valid at the top level, not inside a layer.
If someone wants to work on this I think the following changes would be needed (plus tests): * Move [this](https://github.com/parcel-bundler/lightningcss/blob/400f705e63e139c326f480aed11e1416f5a3a61f/src/parser.rs#L323-L326) from TopLevelRuleParser to NestedRuleParser * Check if `@property` can be...