43081j/postcss-lit

Issues

• SyntaxError: parser error when using `postcss-lit` as Custom Syntax with Stylelint LSP

  #60 opened 2 months ago by florian-sanders
  0

• Stylelint throws error

  #59 opened 4 months ago by evertmonk
  9

• Output not same as postcss-preset-env playground

  #50 opened a year ago by adrianbruntonsagecom
  1

• Comment indentation shifts

  #58 opened 8 months ago by clintcs
  0

• "SyntaxError: Unexpected token" - Using lit x typescript x stylelint

  #49 opened a year ago by KaiSMR
  0

• Can you provide a working example of postcss-lit with tailwindcss?

  #56 opened 10 months ago by flipkickmedia
  4

• Support for `/*css*/` flags

  #55 opened a year ago by RobertAKARobin
  0

• Slashes incorrectly escaped in output?

  #51 opened a year ago by adrianbruntonsagecom
  2

• Vite

  #23 opened 3 years ago by JosefJezek
  11

• Basic usage question

  #48 opened 2 years ago by pathofleastresistor
  1

• Support more variants of css inside lit components

  #47 opened 2 years ago by iSokrat
  6

• Move the package to "lit" project

  #43 opened 2 years ago by iSokrat
  7

• Allow to customise built-in babel config

  #44 opened 2 years ago by iSokrat
  12

• Support decorator syntax when parsing with babel

  #13 opened 3 years ago by 43081j
  12

• Extract the core of postcss-lit to allow other css-in-js syntaxes to be built

  #41 opened 2 years ago by 43081j
  2

• [Bug] stylelint customSyntax postcss-lit deletes custom variables

  #40 opened 2 years ago by danchitiga
  2

• The comment placeholder should be formatted nicely

  #38 opened 2 years ago by 43081j
  0

• Expressions inside values are not mapped back to their original source

  #7 opened 2 years ago by 43081j
  0

• Decide if replacing expressions with a CSS comment is the right decision

  #6 opened 2 years ago by 43081j
  11

• Verify Webpack Documentation

  #34 opened 2 years ago by timbomckay
  2

• Support both keys and value as an expression

  #33 opened 2 years ago by kutnickclose
  5

• Find a way to specify options for the syntax

  #9 opened 3 years ago by 43081j
  1

• Enable parsing jsx files

  #30 opened 2 years ago by kutnickclose
  5

• SyntaxError: Unexpected token

  #29 opened 3 years ago by monsieurnebo
  3

• Hover and focus class definitions get missplaced.

  #26 opened 3 years ago by ma-g-ma
  7

• Is it possible to use this package to process CSS-in-JS with PostCSS?

  #24 opened 3 years ago by veikkoeeva
  7

• Not working on VSCode extension

  #17 opened 3 years ago by abdonrd
  2

• The fix flag breaks the indentation

  #18 opened 3 years ago by abdonrd
  0

• Indentation should account for template position

  #14 opened 3 years ago by 43081j
  0

• Initial release checklist

  #1 opened 3 years ago by 43081j
  5