Core Team

• Lead: @yyx990803
• Planned release: Jan/Feb 2018
• Various improvements regarding error handling, functional components, SSR

• Lead: @yyx990803
• Planned release: March 2018
• Will be targeting evergreen browsers only in order to leverage native ES2015 features
• Reactivity system will be rewritten with Proxies with various improvements
• No major breaking changes; will be maintained in parallel to 2.x with feature parity

• Leveraging more from Web Components when it reaches universal adoption in major browsers (e.g. CLI command that compiles *.vue files into vanilla web components).
• Built-in class-based API when class properties and decorators reach stage 4
• Leveraging Web Assembly when it gains better DOM access capabilities

• Status: beta
• Goal: provide an official library and guide for unit testing Vue components.
• Lead: @eddyerburgh
• Design thread

• Status: in development
• Goal: upgrade vue-cli to address project upgrade issues and provide even smoother DX.
• Lead: @yyx990803, @egoist
• Design thread

• Status: shipped! (Release notes)
• Goal: provide an official eslint plugin with capability of linting single file components (including template syntax errors)
• Lead: @michalsnik, @mysticatea

• Status: in development
• Goal: extract single-file component compilation logic from vue-loader into a bundle-agnostic package so that it can be reused in all tooling in the ecosystem.
• Lead: @znck, @eddyerburgh
• Design thread

• Status: beta
• Goal: offer code style recommendations for teams seeking consistency.
• Lead: @chrisvfritz
• Beta

• Status: in development
• Goal: offer solutions to commonly encountered scenarios
• Lead: @chrisvfritz
• Planned to be started November 2017

• Planned date: Feb. 2018
• Location: Amsterdam, Netherlands
• Contact

• Planned date: Mar. 2018
• Location: New Orleans, Louisiana, USA
• Contact

• Planned date: mid 2018
• Location: London
• Contact

• Planned date: late 2018
• Location: Wrocław, Poland
• Contact