TypeScript 3.7 Nullish Coalescing Operator `? ?` (Double question marks)

SonarQube Cloud
1

We’re seeing errors during the Azure DevOps Code Analysis step on TypeScript files.

Example error:
##[error]ERROR: Failed to parse file [filename removed] at line 126: Expression expected.

Looking at the file/line number, our code shows:
this.lapsedServicers = response ?? new PagedResponse();

It seems the SonarCloud analyizer is getting tripped up on the new ?? nullish coaleascing operator which was added in TypeScript 3.7 – https://github.com/microsoft/TypeScript/pull/32883

Do we know when SonarCloud will be updated to correctly parse TypeScript 3.7 files?

2

Some additional information — We added a step to the Azure DevOps Build Pipeline to install TypeScript to version 3.7.5 prior to the SonarCloud Code Analysis step. However, this causes the SonarCloud Code Analysis step to fail hard with the following errors:

INFO: Sensor Generic Test Executions Report
INFO: Parsing H:\Agents\DEP-1\_work\2\s\Portal\Outsell.Dep.Web.Client\reports\ut_report.xml
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 1:37.593s
INFO: Final Memory: 40M/745M
INFO: ------------------------------------------------------------------------
##[error]ERROR: Error during SonarQube Scanner execution
ERROR: Error during SonarQube Scanner execution
##[error]ERROR: Error during parsing of generic test execution report 'H:\Agents\DEP-1\_work\2\s\Portal\Outsell.Dep.Web.Client\reports\ut_report.xml'. Look at the SonarQube documentation to know the expected XML format.
ERROR: Caused by: H:\Agents\DEP-1\_work\2\s\Portal\Outsell.Dep.Web.Client\reports\ut_report.xml (The system cannot find the path specified)
3

Turns out our missing test execution report was due to a different issue.

Installing TypeScript resolved our issue.