Subroto
## Issue Parser successfully returns for CSS custom properties accompanied by improper Unicode character. ## Current Behaviour ```js await postcss().process(":root { -- : #333; }"); // Returns { ... nodes:...
This extension already supports a minimal setup, i.e. ```jsonc "cssvar.postcssPlugins": [ "tailwindcss/nesting", "tailwindcss" ] ``` This works and it also detects CSS variables dynamically created by **_TailwindCSS plugins_**: --- ##...
Default way of defining plugins using `postcss.config` file: ```jsonc { "plugins: { "autoprefixer": {} // Pass Options as object property value. } } ``` Below is a syntax that Eslint...
Currently, this extension does not integrate properly with VSCode's Settings UI. We need to at least support properties which can use the Settings UI.
Need to test if this issue: https://github.com/stylelint/postcss-css-in-js/issues/294#issue-1331267970 is because of this extension or an issue with postcss parser itself. If it's the latter, will close the issue here, as minimal...
https://user-images.githubusercontent.com/11786283/183144934-e69e7020-59ed-45f6-b8de-924c6003bfc2.mp4
As `postcss-scss` parser only parses the syntax and does not evaluate it, some of the SCSS variable might get missed if they are present inside [SCSS at-rules](https://sass-lang.com/documentation/at-rules). For e.g. the...
`@import` can support a lot of types of CSS functions, and when used with `url` function, it can also be used to fetch CSS from remote URLs. E.g. ```css @import...
> This issue isn't about any errors, thus am not including the issue template details. Can we add `lib/LessParser.js` and other internal modules to `package.json` -> `exports` property. This will...
`cssvar.ignore` can be tedious to maintain, and ignore list can be random for different projects. Adding support for `.gitignore` and `.eslintignore` files opens an opportunity to keep less things inside...