Tooling implementation status

[vjpr]

Thought it would be a good idea to track that status of tools supporting this feature.

• Flow - https://github.com/facebook/flow/releases/tag/v0.54.0
• TypeScript - Implement private fields proposal microsoft/TypeScript#9950
• Babel (7.0.0-beta.48) - Class private properties babel/babel#7842
• IntelliJ/Webstorm - https://youtrack.jetbrains.com/issue/WEB-27687
• Atom
• VSCode
• Sublime - [JavaScript] Add support for class fields sublimehq/Packages#1292
• Acorn - https://github.com/acornjs/acorn-class-fields
• Espree
• Esprima

See all proposals

[alippai]

Should we open acorn, espree and esprima feature requests?

[littledan]

@alippai My understanding was that a lot of tooling had a policy of not implementing until Stage 4. This differs a bit from the policies of a number of web browsers, which may start implementing at Stage 3 and feel comfortable turning it on by default at Stage 4 (though some are more aggressive, and no one has everything in Stage 3 implemented). I'd recommend to tooling projects to adopt a similar policy. However, projects can do whatever they want; if they have a different policy, probably best to respect that in bug reports and keep a policy change discussion separate from these particular features.

[alippai]

Oh, indeed. You are totally right, stage 4 is required for acorn and espree :)

[borela]

As I am using many stage-x features in my projects, I coded a syntax for Sublime Text 3 https://github.com/borela/naomi which highlights even stage-0 features.

[Thom1729]

Sublime's core JavaScript syntax now implements class fields (as of PR 1292).

[adrianheine]

acorn now has class fields support through acorn-class-fields.

[littledan]

This is all great to hear! Does anyone want to post a summary in the README? PRs welcome.

[ephys]

WebStorm has added support for class fields in the latest EAP

[franktopel]

@vjpr I assume this urgently needs a refresh?

[littledan]

@franktopel What updates do you see as needed?

[franktopel]

As far as I can see the current stable version 1.45.0 of VS Code already supports this syntax?

[littledan]

I checked the boxes for TypeScript and VSCode. Thanks for the ping. Any other updates needed?