Eslint-bridge Node.js process is unresponsive -> Increase Timeout?

Hello all
When analyzing a large project, I run into the eslint-bridge Node.js process is unresponsive error. I increased the ram but still the same. When observing the nodejs process, I see that it using some CPU and the RAM is always growing, even when the error occurs. In my opinion, the tasks is still running correctly and just not finished yet but sonarqube runs into an internal timeout. Is there any way to increase the timeout to wait for the eslint-bridge?
Many thanks


  • SonarQube: 8.9.6
  • Scanner: Latest maven or latest standalone
  • JS/TS Plugin: 7.1

Hi, sorry for the late reply. The perf of the scan was improved significantly in 9.x series and the new LTS should come in January. I would suggest upgrading and testing again.


Just for clarity, we expect the new LTS to be released 7 Feb 2023.