-
Notifications
You must be signed in to change notification settings - Fork 936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for TypeScript version 3.7.x - Optional Chaining error #2231
Comments
Hi @CloudPower97, I upgraded to the compiler to use chaining myself. I will test that and get back to you. Hopefully with a fix. |
issue fixed in current version please update. |
Hey @qballer, I've updated both |
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 [email protected] I also hang in our gitter chat here: https://gitter.im/bit-src/Bit |
@CloudPower97 I reproduce the error and get the same error as you from Bit:
@GiladShoham , @davidfirst STP:
|
* resolve #2231, update typescript to support optional chaining * fix lint issues, upgrade some more packages to fix npm-audit * fix eslint issues * fix build-types script * update CHANGELOG
Fixed by updating the typescript version of bit-bin and bit-javascript to 3.7.4.
we get from eslint-parser. Will be part of the next release. |
Describe the bug
I recently moved to
TypeScript
version3.7.3
mainly because ofoptional chaining operator
.However, it seems that even the
react-typescript
compiler version3.1.16
released yesterday has some problem with it.Steps to Reproduce
optional chaining operator
Expected Behavior
It should be possible to use the
optional chaining operator
Screenshots, exceptions and logs
Specifications
The text was updated successfully, but these errors were encountered: