Ilia Kebets

this rule requires to use the codePath API from ESLint, which we aren't very knowledgeable yet.

Sames as https://github.com/SonarSource/SonarJS/issues/2819

another case was reported here: https://community.sonarsource.com/t/javascript-sensor-taking-too-long-at-deploying-the-bridge-server/110316/6

This requires some discussions with other squads and requires specification.

raising issues could be done in another way, but our analysis should be robust!

As discussed, we could also flag objects and arrays whose reference is constant, but that are mutated like: ```js const stack = []; export function foo(num) { stack.push(num); } ```

We're not quite sure what to suggest to users. 1. Using redundant types for developer hints is quite convenient if some value can be several predefined types and custom ones...

This rule might be too noisy. It raises thousands of issues on Peach in TS.

@gabriel-vivas-sonarsource WDYT about adding to the Sonar way?

A related issue is: what happens if we still somehow corrupt the node.js runtime? It will not get overwritten as long as its version is the latest since we perform...