Support for TypeScript version 3.7.x - Optional Chaining error

[CloudPower97]

Describe the bug

I recently moved to TypeScript version 3.7.3 mainly because of optional chaining operator.

However, it seems that even the react-typescript compiler version 3.1.16 released yesterday has some problem with it.

Steps to Reproduce

1. Install the latest TypeScript version (as of now 3.7.3)
2. Try to use the optional chaining operator

Expected Behavior

It should be possible to use the optional chaining operator

Screenshots, exceptions and logs

     > card ...  issues found       
       error found while parsing the file (please edit the file and fix the parsing error): 
          src/components/Card/Filters/index.tsx -> Expression expected.

Specifications

• Bit version: 14.6.0
• Node version: v12.11.1
• yarn version: 1.19.0
• Platform: 5.0.0-37-generic docs(contributing): accurate path in instructions envs#40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
• Compiler / Tester (include version): react-typescript@3.1.16 / bit.envs/testers/jest@22.4.3

[qballer]

Hi @CloudPower97, I upgraded to the compiler to use chaining myself. I will test that and get back to you. Hopefully with a fix.

[qballer]

issue fixed in current version please update.

[CloudPower97]

Hey @qballer, I've updated both bit-bin and react-typescript, but I'm experiencing the same issue.
Thoughts?

[qballer]

It would be great to talk on gitter, I feel that there might be something specific in your work space I need to look at. My email is doron@bit.dev I also hang in our gitter chat here: https://gitter.im/bit-src/Bit

[JoshK2]

@CloudPower97 I reproduce the error and get the same error as you from Bit:

error found while parsing the file (please edit the file and fix the parsing error): 
          src/getAnimalType.ts -> Expression expected.

@GiladShoham , @davidfirst
The error is with Bit parsing and not with the compiler, because if I run bit build with the React-TypeScript compiler (3.1.28) it's built correctly the component, but I cannot tag it because of the parsing error.

STP:

1. Create a TypeScript project.
2. Create a simple TS file and put this function inside;

export const getAnimalType = (animal: Record<string, any>, name: string): string => {
    return animal[name]?.type;
}

3. Track this component and run bit status, you should get the same error as we get.