Tooling implementation status

[vjpr]

Links to "Tooling implementation status" issues for some proposals, so people can see whether their tools support the proposals. I check them when they are supported in WebStorm, Babel and Flow.

• Tooling implementation status proposal-class-fields#57
• Tooling implementation status proposal-private-methods#32
• Tooling implementation status proposal-optional-chaining#44
• Tooling implementation status proposal-nullish-coalescing#29
• Tooling implementation status proposal-pipeline-operator#123
• Tooling implementation status proposal-pattern-matching#107
• Tooling implementation status proposal-throw-expressions#11

By tool

• Babel - https://github.com/babel/proposals
• WebStorm - https://youtrack.jetbrains.com/issues/WEB?q=tag:%20ESNext
• Flow - TC39 proposals status facebook/flow#6258
• VSCode
• Typescript
• Sublime - [JavaScript] ECMAScript Omnibus sublimehq/Packages#1269

[ljharb]

Typically this is something each individual proposal should be tracking on its own repo.

[mathiasbynens]

The proposals I author or champion include an “implementations” section in the README that link to open bugs or list implementation status in JavaScript engines, web browsers, and tooling such as Babel. I wouldn’t mind if this became a requirement.

Note that Stage 4 already requires multiple implementations, so it’s only a small step to require listing that info in the repository somewhere.

[vjpr]

@ljharb Typically this is something each individual proposal should be tracking on its own repo.

This is the idea behind this issue. It links to tracking issues in other proposal's repos. Have a look.

Having an issue like this open in proposal repos allows people to make comments when the status needs to change. Its worked well for 6 months.

Ideally this should be replicated in the readme though in a standard way as @mathiasbynens
suggests. Maybe something like docs/implementations.md with a link at the top of the proposal. And then these issues can be used for people to comment on implementation status changes.

[xtuc]

Copying my comment here: tc39/proposal-pipeline-operator#123 (comment).

FYI we are wanting to centralizing the implementation status on the future TC39 website: https://github.com/tc39/tc39-web-draft. Tracking will be easier.

[oyilmaztekin]

I want to take action on this issue. Considering the ideas from here and from other issues that is related, perhaps we can start off creating a markdown file in this repo to organize "implementation status". Consequently, it can be used for crawlers of beta website or some informative section of this repo. Either way, it needs to be clarified how we can move forward.

Related issues:
beta/#61
beta#59
beta#60