node is not available in your
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 SonarCloud instance it will conflict with analysis of CSS, so it should be removed.
Discover and update the CSS properties in: Project Administration > General Settings > Languages > CSS.
Supported Frameworks and Versions
- 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 stacktrace might appear in the logs
ERROR: Failed to get response while analyzing [file].ts java.io.InterruptedIOException: timeout
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. The
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 (LCOV format)
- SonarJS Plugin for ESLint