# Getting an Error in sonarcloud Analyzer **URL:** \ **Category:** SonarQube Cloud\ **Tags:** sonarqube-cloud, coverage\ **Created:** [April 5, 2022, 10:07am UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095 "2022-04-05T10:07:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![SWARAJ\_SIRSAT](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/swaraj_sirsat/32/32100_2.png) [@SWARAJ\_SIRSAT](https://community.sonarsource.com/u/SWARAJ_SIRSAT)\ **Post date:** [April 5, 2022, 10:07am UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/1 "2022-04-05T10:07:52Z")
we are doing a project where for a few months I am getting an error in the sonar cloud analyzer the error is like, tried but not working please guide me if anyone knows the solution: ```auto INFO: 'sonar.coverage.jacoco.xmlReportPaths' is not defined. Using default locations: target/site/jacoco/jacoco.xml,target/site/jacoco-it/jacoco.xml,build/reports/jacoco/test/jacocoTestReport.xml INFO: No report imported, no coverage information will be imported by JaCoCo XML Report Importer INFO: Sensor JaCoCo XML Report Importer [jacoco] (done) | time=3ms INFO: Sensor JavaScript analysis [javascript] INFO: Deploying custom rules bundle jar:file:/home/vsts/.sonar/cache/5b5e29635f902671c7f854f03c57c474/sonar-securityjsfrontend-plugin.jar!/js-vulnerabilities-rules-1.0.0.tgz to /home/vsts/work/1/s/.scannerwork/.sonartmp/eslint-bridge-bundle/package/custom-rules12698087724236910895 ##[error]ERROR: **internal/modules/cjs/loader.js:796** ERROR: throw err; ERROR: internal/modules/cjs/loader.js:796 ##[error]ERROR: ^ ERROR: ERROR: Error: Cannot find module 'eslint/use-at-your-own-risk' ERROR: Require stack: ``` ---
**Author:** ![bruno.mendola](https://avatars.discourse-cdn.com/v4/letter/b/ecccb3/32.png) [@bruno.mendola](https://community.sonarsource.com/u/bruno.mendola)\ **Post date:** [April 5, 2022, 3:47pm UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/3 "2022-04-05T15:47:35Z")
Same here. Using: SonarQube CE 9.4, node v12.14.0, yarn 1.22.18 and sonarqube-scanner 2.8.1. ---
**Author:** ![Manish\_Mangyani](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/manish_mangyani/32/32145_2.png) [@Manish\_Mangyani](https://community.sonarsource.com/u/Manish_Mangyani)\ **Post date:** [April 6, 2022, 6:39am UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/4 "2022-04-06T06:39:20Z")
Hi Team, This is the addition of the errors for the above errors Our DevOps pipelines are facing issues for the last 1 month. Could you please check and let us know the resolution as we are paying for it and there is no other support option I can find for paid customers ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/4/8/48bd587e7a1a030794fa32155630db61c3129dd0.png) ---
**Author:** ![bruno.mendola](https://avatars.discourse-cdn.com/v4/letter/b/ecccb3/32.png) [@bruno.mendola](https://community.sonarsource.com/u/bruno.mendola)\ **Post date:** [April 6, 2022, 3:16pm UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/5 "2022-04-06T15:16:56Z")
Update: solved by upgrading node v12.14.0 to v12.22.11 ---
**Author:** ![Manish\_Mangyani](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/manish_mangyani/32/32145_2.png) [@Manish\_Mangyani](https://community.sonarsource.com/u/Manish_Mangyani)\ **Post date:** [April 7, 2022, 1:38pm UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/6 "2022-04-07T13:38:45Z")
> [@bruno.mendola](#): > > 12.22.11 Thank you so much… it worked! ---
**Author:** ![SWARAJ\_SIRSAT](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/swaraj_sirsat/32/32100_2.png) [@SWARAJ\_SIRSAT](https://community.sonarsource.com/u/SWARAJ_SIRSAT)\ **Post date:** [April 8, 2022, 4:47am UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/7 "2022-04-08T04:47:44Z")
Thank you so much. ---
**Author:** ![xuy22](https://avatars.discourse-cdn.com/v4/letter/x/258eb7/32.png) [@xuy22](https://community.sonarsource.com/u/xuy22)\ **Post date:** [June 1, 2022, 8:40am UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/9 "2022-06-01T08:40:43Z")
> [@bruno.mendola](#): > > pdate: solved by upgrading node v12.14.0 to v12.22.11 Hi Bruno, My name is Ken and I am a total comes to SonarQube. I am having the same issue when upgrade from 9.2 to 9.4, and when you talk about updating node from v12.14.0 to v12.22.11. what does that mean? is this something to be configured inside the yml pipeline? sorry again to ask such stupid question. thank you Regards, Ken ---
**Author:** ![victor.diez](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/victor.diez/32/38525_2.png) [@victor.diez](https://community.sonarsource.com/u/victor.diez)\ **Post date:** [June 13, 2022, 12:13pm UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/11 "2022-06-13T12:13:27Z")
Hello @xuy22, You need to download and install Node.js from the [official website](https://nodejs.org/download/release/v12.22.12/). Install it in the machine where the analysis are running. Please let me know if that works. Best regards, Victor ---
**Author:** ![xuy22](https://avatars.discourse-cdn.com/v4/letter/x/258eb7/32.png) [@xuy22](https://community.sonarsource.com/u/xuy22)\ **Post date:** [June 13, 2022, 9:27pm UTC](https://community.sonarsource.com/t/getting-an-error-in-sonarcloud-analyzer/61095/12 "2022-06-13T21:27:52Z")
Hi Victor, Thank you so much. I will give that a go and might come back with more questions. thanks again Regards, Ken