Tooling implementation status
vjpr opened this issue · 7 comments
Thought it would be a good idea to track that status of tools supporting this feature.
- Flow (0.71.0 - gated behind the
esproposal.optional_chaining) - facebook/flow#4303 (comment) - Babel (7) - babel/babylon#545 / babel/babel#5813
- Typescript - microsoft/TypeScript#16 (not until stage-3)
- Webstorm (2017.3) - https://youtrack.jetbrains.com/issue/WEB-27592
- Sublime Text (3) - sublimehq/Packages#2132
Awesome to have these references in one place! IMO it wouldn't hurt to put it in the README as well.
I want to point out that Typescript team will not implement the tooling until this proposal is in stage-3.
FYI, Sublime Text probably will not implement this until it hits Stage 3 or there's a working implementation (Babel counts).
@Thom1729 I am already using the feature without issues in Sublime Text 3, through babel 7, eslint, babel-eslint v8.2.1 and SublimeLinter. There is a known regresion in babel-eslint v8.2.2 that prevents it from working currently, but that's not linked to Sublime Text: babel/babel-eslint#595
There are some third-party packages that support the optional chaining syntax, whether by design or by coincidence. I meant to speak of the first-party JavaScript syntax, which does not support the syntax. See this issue for more information.
Flow supports optional chaining (mostly). See facebook/flow#4303 (comment).
It's implemented in TypeScript (at least on v3.7.3) so I believe the TS checkbox should be updated.
It's also supported on VSCode, not sure about ST3.