Text of code.visualstudio.com › updates › v1_59 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

July 2021 (version 1.59)

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. July 2021 (version 1.59) Update 1.59.1 : The update addresses these issues . This release also addresses CVE-2021-26437 . Downloads for 1.59.1 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the July 2021 release of Visual Studio Code. There are many updates in this version that we hope you will like, some of the key highlights include: Extensions view improvements - Rich extension detail hovers, new runtime status tab.

Settings editor validation - Quickly find editing errors for object-based settings. Drag and drop terminals - Move terminals across windows to both editor and panel areas. Extended theme customization - Customize multiple color themes at once. Built-in support for Jupyter notebooks - Open .ipynb files directly in VS Code. Notebook UI improvements - Display first line of collapsed cells, Undo/Redo per cell. Testing API finalized - Native support for running tests in VS Code with built-in Test Explorer.

Debug Disassembly view preview - Display disassembled C++ code in VS Code. Live Preview extension - Live HTML preview within VS Code with JavaScript debugging support. Dev Containers devcontainer CLI - Command line interface for working with development containers. If you'd like to read these release notes online, go to Updates on code.visualstudio.com . Join us live at the VS Code team's livestream on Tuesday, August 10 at 8am Pacific (4pm London) to see a demo of what's new in this release, and ask us questions live.

Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. Workbench Extensions Improved Extensions view on resize. In the following short video, the Extensions view with default width shows all details (previously the icon, ratings, and install count were not shown). As the view shrinks, a smaller extension icon is shown, and when its width reduces further, the icon and ratings are hidden.

Theme: GitHub Light Theme The Extensions view now shows a custom hover on an extension. This rich hover includes the complete description of the extension and other useful information such as why an extension is disabled or recommended. Theme: GitHub Light Theme You can now check the runtime status of an extension in the new Runtime Status tab in the extension pane. Status information includes its activation time, whether it is activated on startup, and if it has any warnings or errors.

Some of this information is displayed in the Extensions view and its hover (shown in the image above). Theme: GitHub Light Theme The Extension pane Details tab now shows categories, resources links, and other information such as the extension release and update dates. Selecting a category will display other extensions in that category in the Extensions view. Theme: GitHub Light Theme Settings editor The Settings editor now supports validation on objects.

The validation checks for type errors that can be introduced when editing the JSON file directly. Array settings now have drag and drop support in non-editing mode. Moreover, enum array settings with the property uniqueItems set to true now only show remaining options rather than all options in the dropdowns: The Settings editor also now supports multiline string settings, where the value is rendered in a multiline text area instead of a single-line input box: Extended theme customization syntax The color customization settings listed below allow users to customize colors of the current theme: workbench.colorCustomizations editor.tokenColorCustomizations editor.semanticTokenColorCustomizations There is new syntax to customize multiple themes at once: "workbench.colorCustomizations" : { "[Abyss][Red]" : { "activityBar.background" : "#ff0000" }, "[Monokai*]" : { "activityBar.background" : "#ff0000" } }, Multiple themes can be listed as well as the * wildcard character can be used at the beginning and the end of the name.

Support for Jupyter Notebooks This month, we moved the code that handles reading *.ipynb files from the Jupyter Notebook extension into a new built-in extension. This means that you can now open Jupyter notebooks in a clean install of VS Code, without having to install the full Jupyter extension. However, if you want to execute cells or view outputs that use ipywidgets or other complex renderer types, you will have to install the Jupyter extension.

Notebook layout improvements We have made a few improvements to the notebook layout this iteration: The first line of the cell input is now rendered when the cell is collapsed. Actions on the notebook editor toolbar will be moved into the overflow menu ( ... ) when the window is not wide enough to render all primary actions. The default value of notebook.undoRedoPerCell is now changed to true . We also updated the default styles for code cells and now show a background color to help distinguish cells apart.

Themes can use notebook.cellEditorBackground to customize this color. Lastly, you can now toggle the text labels on the notebook toolbar using the setting notebook.globalToolbarShowLabel : Configure the path separator for Copy Relative Path A new setting explorer.copyRelativePathSeparator allows you to explicitly set the path separator when invoking the Copy Relate Path action. The available separator options are: auto (default) - Uses operating system specific path separation character. / - Use slash as the path separation character. \\ - Use backslash as the path separation character.

Share view state across editor groups A new setting workbench.editor.sharedViewState was added to configure how editor view state (for example, the scroll position in the editor) is shared across editor groups. By default, this setting is disabled to preserve the current behavior. If you open an editor to the side and close that editor group later, only to open the editor again to the side, no view state is restored because you are opening a new editor group.

However, when you enable this setting, the most recent editor view state is preserved across all editor groups and will be used, unless more specific view state is found for the editor group. Below the selection state is preserved when reopening the package.json file to the side. Editor Navigate between folding regions There are new commands to set the cursor location to a corresponding fold: Go to Next Fold ( editor.gotoNextFold ) Go to Previous Fold ( editor.gotoPreviousFold ) Go to Parent Fold ( editor.gotoParentFold ) The commands currently have no default keybindings but you can add you own keyboard shortcuts via Preferences: Open Keyboard Shortcuts ( ⌘K ⌘S (Windows, Linux Ctrl+K Ctrl+S ) ).

Automatically fold imports Use the setting editor.foldingImportsByDefault to have import statements automatically folded. The fold state is stored once a file has been opened once. The feature works with TypeScript, JavaScript, Java, C#, C++, and with all languages that have a folding range provider that annotates import statements with FoldingRangeKind.Imports . Seed search string from selection The Find control setting editor.find.seedSearchStringFromSelection has been extended to support seeding the search string only from non-empty selection.

By default, the editor will use the selection or the word around the empty selection as the search keyboard when the Find control is revealed. Inline suggestions improvements We have changed the way inline suggestions are rendered. This not only fixes a lot of bugs, but also makes word wrapping aware of inline suggestions. In addition, multi-line inline suggestions at non-trailing positions are now supported. Inlay hints improvements We have also changed the way inlay hints are rendered.

By using the same mechanism as for inline suggestions, inlay hints are now also taken into account for word

The rest of this page is on the live site.