node is not available in the
PATH, you can use property
sonar.nodejs.executable to set an absolute path to Node.js executable.
If you have a community plugin for CSS analysis installed on your SonarQube instance it will conflict with analysis of CSS, so it should be removed.
Discover and update the CSS properties in Administration > General Settings > CSS.
Supported frameworks, versions and languages
- ECMAScript 3, 5, 2015, 2016, 2017, 2018, 2019, and 2020
- TypeScript 4.9.4
- React JSX, Vue.js, Angular
- CSS, SCSS, Less, also 'style' inside PHP, HTML and VueJS files
Slow or unresponsive analysis
On a big project, more memory may need to be allocated to analyze the project. This would be manifested by analysis getting stuck and the following stack trace might appear in the logs
You can use
8192 for big projects. This property should be set in
sonar-project.properties file or on command line for scanner (with
Default exclusions for JS/TS
By default, analysis will exclude files from dependencies in usual directories, such as
external. It will also ignore
.d.ts files. If for some reason analysis of files in these directories is desired, it can be configured by setting
sonar.exclusions property will exclude all files.
sonar.exclusions property should be preferred to configure general exclusions for the project.
Custom rules for JS/TS
Custom rules are not supported by the analyzer. As an alternative we suggest you to have a look at ESLint, it provides custom rules that you can then import thanks to the External Issues feature.
- Importing external issues (ESLint, TSLint, StyleLint)
- Test coverage and execution (LCOV format)
- SonarJS plugin for ESLint
- Adding coding rules
© 2008-2023, SonarSource S.A, Switzerland. Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution-NonCommercial 3.0 United States License. SONARQUBE is a trademark of SonarSource SA. All other trademarks and copyrights are the property of their respective owners.