43081j / postcss-lit

PostCSS syntax for extracting CSS from template literals inside JS/TS files

43081j/postcss-lit Issues

"SyntaxError: Unexpected token" - Using lit x typescript x stylelint
Updated 3 months ago
Can you provide a working example of postcss-lit with tailwindcss?
Updated 3 months ago4
Support for `/*css*/` flags
Updated 5 months ago
Slashes incorrectly escaped in output?
Closed 7 months ago2
Vite
Updated 7 months ago11
Output not same as postcss-preset-env playground
Updated 7 months ago
Basic usage question
Updated a year ago1
Support more variants of css inside lit components
Updated a year ago6
Move the package to "lit" project
Updated a year ago7
Allow to customise built-in babel config
Closed a year ago12
Support decorator syntax when parsing with babel
Closed 3 years ago12
Extract the core of postcss-lit to allow other css-in-js syntaxes to be built
Updated a year ago2
[Bug] stylelint customSyntax postcss-lit deletes custom variables
Updated 2 years ago2
The comment placeholder should be formatted nicely
Closed 2 years ago
Expressions inside values are not mapped back to their original source
Closed 2 years ago
Decide if replacing expressions with a CSS comment is the right decision
Closed 2 years ago11
Verify Webpack Documentation
Updated 2 years ago2
Support both keys and value as an expression
Closed 2 years ago5
Find a way to specify options for the syntax
Updated 2 years ago1
Enable parsing jsx files
Closed 2 years ago5
SyntaxError: Unexpected token
Updated 2 years ago3
Hover and focus class definitions get missplaced.
Closed 2 years ago7
Is it possible to use this package to process CSS-in-JS with PostCSS?
Updated 2 years ago7
Not working on VSCode extension
Closed 3 years ago2
The fix flag breaks the indentation
Closed 3 years ago
Indentation should account for template position
Closed 3 years ago
Initial release checklist
Closed 3 years ago5