proposal-class-fields Tooling implementation status

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

[x] Flow - https://github.com/facebook/flow/releases/tag/v0.54.0
[x] TypeScript - https://github.com/Microsoft/TypeScript/issues/9950
[x] Babel (7.0.0-beta.48) - https://github.com/babel/babel/pull/7842
[x] IntelliJ/Webstorm - https://youtrack.jetbrains.com/issue/WEB-27687
[ ] Atom
[x] VSCode
[x] Sublime - https://github.com/sublimehq/Packages/pull/1292
[x] Acorn - https://github.com/acornjs/acorn-class-fields
[ ] Espree
[ ] Esprima

Nov 08 '17 11:11 vjpr

Should we open acorn, espree and esprima feature requests?

Nov 18 '17 23:11 alippai

@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.

Nov 21 '17 11:11 littledan

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

Nov 21 '17 11:11 alippai

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.