|
- September 2016 (version 1. 6) - Visual Studio Code
The old outDir is still supported, but we plan to deprecate this in the future The following example shows how to configure source maps if the generated code lives in an "out" and "node_modules" directory and you want to exclude the generated test code:
- September 2017 (version 1. 17) - Visual Studio Code
Welcome to the September 2017 release of Visual Studio Code There are a number of significant updates in this version that we hope you will like, some of the key highlights include: macOS Touch Bar support - Touch Bar actions for navigation and debugging Source code folding improvements - Collapse region markers and off-side language blocks
- January 2017 (version 1. 9) - Visual Studio Code
Welcome to the first 2017 release of Visual Studio Code There are a number of significant updates in this version that we hope you will like, some of the key highlights include: New Welcome page - Whether you are a new or returning user, the Welcome page helps get you started quickly
- November 2016 (version 1. 8) - Visual Studio Code
Use the 'old' debugger node when debugging Node js versions < 6 3 and the new debugger node2 for versions >= 6 3 Note: If you are using ES6 Proxy in your Node js app, a Node js v7 x runtime might even crash when being debugged by the old debugger
- May 2019 (version 1. 35) - Visual Studio Code
Note that the old, hard-coded behavior was to reuse the current editor and the default for revealIfOpen is not to reuse The Peek view now supports search and filter, like the results tree, to allow you to quickly narrow down on a result
- June 2017 (version 1. 14) - Visual Studio Code
We will still support the old setting for a couple of releases Close unmodified files A new command was introduced to close unmodified editors of the currently active editor group This makes it easy to quickly dismiss tabs of editors that are not dirty (no unsaved changes)
- December 2015 (0. 10. 6) - Visual Studio Code
You can still use the old setting but we ask you to update to the new name Themes Various fixes to the default light and dark theme Due to the move to TextMate tokenizers in the last release, there were changes in the appearance of the default light and dark theme
- November 2021 (version 1. 63) - Visual Studio Code
The old settings terminal integrated automationShell * have been deprecated and new terminal integrated automationProfile * settings have been added This allows for greater freedom in specifying properties of terminals used for tasks, including shell, icon, color, and shell argument
|
|
|