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.
- ECMAScript 3, 5, 2015, 2016, 2017, 2018, 2019, 2020, 2021 and 2022
- TypeScript 5.0
- React JSX, Vue.js, Angular
- CSS, SCSS, Less, also 'style' inside PHP, HTML and VueJS files
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
You can use
8192 for big projects. This property should be set in
sonar-project.properties file or on command line for scanner (with
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.
By default, analysis will exclude all files whose size is greater than 1000 KB. To change this limit, set the
The analyzer will attempt to detect bundled code or generated code. This means code that was automatically transformed and optimized with tools such as Webpack and similar. We consider generated code out of scope of the analysis since developers are not able to act upon the findings in such code. Whenever generated code is detected, the analysis will print a log message: once per the whole project on
INFO level, and for each file on the
DEBUG level. If you want to opt-in for analyzing the generated code or in case the detection is incorrect, you can disable it by setting