Roadmap

With the "1.0" release behind us, now is a good time to look towards the future. We typically look out 6 to 12 months, establish a set of themes we want to work towards, and then schedule work each milestone supporting those themes. VS Code will continue to ship monthly and we'll make progress against each of the following themes during each iteration.

Improve the Getting Started Experience

It should be quick and natural to customize VS Code to the way you work so that you can quickly get started working on your code.

• Help to configure key bindings, themes, common settings on first run of VS Code
• Ability to create new and populated Workspaces from within VS Code
• 🏃 "Open in VS Code" from a git repository

Eliminate Adoption Blockers

VS Code is a young product and there still missing features and experiences that you are asking for and that we want to deliver.

• Tabs
• Integrated Terminal
• Move error list from Quick Box to a panel
• Indent guides
• Global Replace
• 🏃 Support for VIM style key bindings
• 🏃 Temp file storage when editor is closed
• Multiple folders inside a single workspace
• 🏃 Editor layout (e.g. horizontal split)
• Search performance improvements file list/contents
• 🏃 Workbench theming, e.g.,support icons in explorer
• Accessibility
• Improved settings and configuration experiences

Improved Extension creation, discovery and management

We want to make it easy for developers to create extensions and for users to discover extensions. And, once you have discovered a set of extensions, we want to make it easy for you to manage them.

• In product extension management experience
• Improved extension recommendation experience
• 🏃 Support for disabling an extensions vs. uninstall
• Update all extensions and keep all extensisons up-to-date actions
• 🏃 Support for "extension packs”, collections of extensions and settings
• Improved documentation for language based extensions
• Improve the Marketplace experience for discovering and installing extensions

For extension developers:

• SDK: Improve extension README authoring and quality
• Expand the core VS Code extensibility APIs

• Menu contributions
• File Icon sets
• 🏃 Support for extensions to programmatically update settings files

• Expand the diagnostics experience and API to support additional debugging scenario requirements, such as

• attach to process

Monaco Editor

• We will also make it easy to consume and ship the core code editor ("Monaco") as a library.

TypeScript, JavaScript, and Node development

We will continue to improve our code editing and navigation experiences by partnering with the TypeScript team on the Salsa language service. We will also continue to enhance our end-to-end debugging experiences for Node applications.

• Work with the TypeScript team on the JavaScript language service which powers our JavaScript and TypeScript editing experiences to:

  • 🏃 Suggest imports of .d.ts files to enable IntelliSense "out of the box"
  • Angular IntelliSense
  • Suggest project configuration files (jsconfig.json, tsconfig.json)
  • Show errors for the entire project and not only the file that is currently edited.

• Node Debugger: Step over uninteresting (generated) code

• Improved npm support and help to keep the package.json consistent with the installed node modules

Engineering Items

We will continue to improve the engineering of VS Code itself and add items as needed:

• Improve crash logging
• Improve crash diagnostics (e.g. client side log).

Summary

These are examples of just some of the work we will be focusing on in the next 6 to 12 months. We will provide much more detail in each of our monthly iteration plans so follow along and let us know what you think!