-
Updated
Feb 5, 2021 - CSS
postcss
Here are 1,934 public repositories matching this topic...
-
Updated
Dec 12, 2020 - JavaScript
-
Updated
Mar 18, 2019 - JavaScript
-
Updated
Feb 4, 2021
-
Updated
Nov 8, 2020 - JavaScript
-
Updated
Feb 27, 2020 - HTML
-
Updated
Feb 2, 2021 - JavaScript
Describe the bug
Keyframes names like those h1{ -webkit-animation: e836684w2 } h2{ animation: e836684w2 } with e at beginnig are trying to convert by postcss-convert-values
To Reproduce
Here is PR with failing test on this case
cssnano/cssnano#908
Expected behavior
Expected that no conversion performed
Screenshots
**Desktop (please comp
-
Updated
Dec 11, 2020 - JavaScript
-
Updated
Sep 29, 2017 - CSS
Would be great if you could create a custom plugin for stylelint that adds support for your custom rules; for example, making font-range a known property for the property-no-unknown rule.
-
Updated
Dec 31, 2020 - TypeScript
-
Updated
Dec 3, 2020 - JavaScript
-
Updated
Dec 15, 2020 - JavaScript
-
Updated
Jan 22, 2021 - JavaScript
-
Updated
Jan 26, 2021 - JavaScript
-
Updated
Feb 4, 2021 - JavaScript
-
Updated
Dec 10, 2020 - TypeScript
-
Updated
Feb 3, 2021 - TypeScript
-
Updated
Jan 28, 2021 - JavaScript
-
Updated
Jul 16, 2020 - CSS
Improve this page
Add a description, image, and links to the postcss topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the postcss topic, visit your repo's landing page and select "manage topics."
I think it would be better if this rule supports the ability to check CSS custom properties. For example we have color palette from designers with long complex naming. In this case, it is easy to make the mistake.