From f0bd3c0e8efd7192570a126605bf3ea61eff1b84 Mon Sep 17 00:00:00 2001 From: Elena Vilchik Date: Fri, 14 Jun 2019 16:18:08 +0200 Subject: [PATCH] [DOC] Update property for NodeJS for CSS (#1747) Since sonar-css 1.1 --- server/sonar-docs/src/pages/analysis/languages/css.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/sonar-docs/src/pages/analysis/languages/css.md b/server/sonar-docs/src/pages/analysis/languages/css.md index 2fe4bc5a5cf..70e310b41ce 100644 --- a/server/sonar-docs/src/pages/analysis/languages/css.md +++ b/server/sonar-docs/src/pages/analysis/languages/css.md @@ -10,7 +10,7 @@ url: /analysis/languages/css/ ## Prerequisites -In order to analyze CSS code, you need to have Node.js >= 6 installed on the machine running the scan. Set property `sonar.css.node` to an absolute path to Node.js executable, if standard `node` is not available. +In order to analyze CSS code, you need to have Node.js >= 6 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 SonarCSS, so it should be removed. -- 2.39.5