Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>language-postcssNew to Visual Studio Code? Get it now.
language-postcss

language-postcss

Li Chen

|
116,613 installs
| (6) | Free
PostCSS language support
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

I'm not using postcss anymore, it's a long story, but I switched to sass. Contact me if you are interested in this project and willing to help.

language-postcss

Adds syntax highlighting to PostCSS files in Visual Studio Code.

Using PostCSS in Visual Studio Code

For the best in-editor experience, use this extension in combination with stylelint which will provide general (Post)CSS linting/syntax checks.

Add a .stylelintrc file to your project to configure rules. For a good set of maintained rules, install this npm package to your project:

npm i -D stylelint-config-recommended

Then you can extend that set of rules and just override the ones you want to change:

{
  "extends": "stylelint-config-recommended",
  "rules": {
    ...
  }
}

If you are using any non-standard postcss modules, you can use the file extensions .pcss or .postcss to prevent VSCode's built-in CSS parser from showing unwanted errors.

If you want syntax checks for postcss-nesting (i.e., require the & character) you can add this rule:

{
  "extends": "stylelint-config-recommended",
  "rules": {
    "selector-nested-pattern": "^&"
  }
}

Use PostCSS syntax highlighting in *.css files

To enable PostCSS syntax highlighting in *.css files, add the following to your VS Code settings:

  "files.associations": {
    "*.css": "postcss"
  }

TODO

  • [ ] Add completion for selectors, variables, properties etc.

Credits

This is a clone of PostCSS syntax with minor changes.

The original extension does not have a github repository, so open source collaboration is impossible. This is the main reason I created this clone.

snapshot

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft