Hello Vladislav,
Happy new year!
The “react-jsx” option has been introduced in the Typescript 4.1 version, which I assume you are using. The JS analyzer embeds Typescript 3.8.3, that’s why it doesn’t understand the option and can not run the analysis. We plan to update Typescript to the latest version, but we don’t have an ETA.
One possible temporary workaround would be to duplicate your existing tsconfig.json file. You could then change the “jsx” property to use “react”, and tell the analyzer to use this new tsconfig.json, by using the sonar.typescript.tsconfigPath property. You can configure this value with the scanner as any other property or through SonarLint in Settings > Tools > SonarLint > Project Settings > Analysis properties.
I’m afraid we can’t provide a better alternative for the moment.
About your test files that are not analyzed, using the include should be sufficient (it works for me). It might be related to use of SonarTS, do you observe the same problem when not connected to SonarQube ? Was your company able to update the plugins on SonarQube side ?