# CSS

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

In order to analyze CSS code, you need to have Node.js >= 8 installed on the machine running the scan. Set property `sonar.nodejs.executable` to an absolute path to Node.js executable, if standard `node` is not available.

If you have a community plugin that handles CSS installed on your SonarQube instance it will conflict with analysis of CSS, so it should be removed.

## Language-Specific Properties <a href="#language-specific-properties" id="language-specific-properties"></a>

Discover and update the CSS-specific [properties](/sonarqube-server/8.9/analyzing-source-code/analysis-parameters.md) in: **Administration > General Settings > CSS**

## Supported languages <a href="#supported-languages" id="supported-languages"></a>

* CSS, SCSS, Less
* Also ‘style’ inside PHP, HTML and VueJS files

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Importing third-party issues](/sonarqube-server/8.9/analyzing-source-code/importing-external-issues/importing-third-party-issues.md) (StyleLint.io)

## Issue tracker <a href="#issue-tracker" id="issue-tracker"></a>

Check the [issue tracker](https://github.com/SonarSource/sonar-css/issues) for this language.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/8.9/analyzing-source-code/languages/css.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.