Text of code.visualstudio.com โ€บ updates โ€บ v1_26 as Styx crawled it on Oct 10, 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 2018 (version 1.26)

๐ŸŽฌ Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. July 2018 (version 1.26) Update 1.26.1 : The update addresses these issues . Downloads for 1.26.1 Windows x64 macOS Intel Linux 64-bit .deb .rpm .tar.gz Linux 32-bit .deb .rpm .tar.gz Welcome to the July 2018 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: Breadcrumbs - Breadcrumb navigation lets you jump to symbols and files in your workspace.

Quick Fixes from Problems panel - Apply code fixes while reviewing warnings and errors. User setup on Windows - Elevation no longer required during Windows setup. Terminal column selection - Alt+click to select blocks of text in the integrated terminal. Add all missing imports - Single action to add all missing imports in a JavaScript/TypeScript file. JSX tag completion - Work with JSX tags in JavaScript/TypeScript just like you do in HTML.

Better JS/TS error reporting - Concise, clear messages with relevant source code links. Improved extension search - Filter Marketplace queries to find the extensions you want. Extension Pack management - Manage Extension Packs as a single unit or by individual extension. Preview: Settings editor - Rich settings description display, "Table of Contents" tracks scrolling. If you'd like to read these release notes online, go to Updates on code.visualstudio.com .

You can also check out this 1.26 release highlights video from Cloud Developer Advocate Brian Clark . The release notes are arranged in the following sections related to VS Code focus areas. Here are some further updates: Workbench - New View menu layout, copy relative path action, offline mode. Integrated Terminal - Improved multiline support, rendering improvements. Languages - Convert named imports to namespace imports, JSX folding.

Debugging - Improved stop session and smart step debugging. Preview Features - Themable custom tool and menu bar for Windows and Linux. Extension Authoring - QuickInput API, extensionPack declaration, webview titlebar icons. Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. And for the latest Visual Studio Code news, updates, and content, follow us on Twitter @code !

Workbench Breadcrumbs The editor now has a navigation bar above its contents - we call it Breadcrumbs . It shows the current location and allows you to quickly navigate between symbols and files. To start using breadcrumbs, enable it with the View > Show Breadcrumbs command or via the breadcrumbs.enabled setting. When using editor tabs (default), breadcrumbs are displayed in a separate row below the editor title. If you are not using editor tabs, breadcrumbs show as an interactive file path next to the title.

Breadcrumbs always show the file path and, with the help of extensions, the symbol path up to the cursor position. The symbols shown are the same as in Outline view and Go to Symbol and so existing extensions will just work with breadcrumbs. The appearance of breadcrumbs can be customized. If you have very long paths or are only interested in either file paths or symbols paths, you can use the breadcrumbs.filePath and breadcrumbs.symbolPath settings.

Both support on , off , and last and they define if or what part of the path you see. To interact with breadcrumbs, use the Focus Breadcrumbs command or press โ‡งโŒ˜. (Windows, Linux Ctrl+Shift+. ) . It will select that last element and open a dropdown that allows you to navigate to a sibling file or symbol. Use the โ† (Windows, Linux Left ) and โ†’ (Windows, Linux Right ) keyboard shortcuts to go to elements before or after the current element.

When the dropdown appears, simply start typing - all matching elements will be highlighted and the best match will be selected for quick navigation. You can also interact with breadcrumbs without the picker. Press โ‡งโŒ˜; (Windows, Linux Ctrl+Shift+; ) to focus the last element, use โ† (Windows, Linux Left ) and โ†’ (Windows, Linux Right ) to navigate, and use Space to reveal the element in the editor. Problems panel Quick Fixes You can now apply Quick Fixes from the Problems panel.

A light bulb indicating Quick Fixes is shown when you hover or select a problem entry. Quick Fixes can be applied by clicking on the light bulb or by opening the context menu for the problem entry. Note: The light bulb indicator is shown only if the extension contributing Quick Fixes provides Diagnostic information associated with the Quick Fix. User setup for Windows Announced last release, the user setup package for Windows is now available on stable.

Installing the user setup does not require Administrator privileges as the location will be under your user Local AppData (LOCALAPPDATA) folder. User setup also provides a smoother background update experience. Download User Setup If you are a current user of the system-wide Windows setup, you will be prompted to install user setup, which we recommend using from now on. Don't worry, all your settings and extensions will be kept during the transition.

During installation, you will also be prompted to uninstall the system-wide setup. Grid: Automated maximize of minimized editors One feature we lost during the introduction of the grid editor layout last milestone was the ability to have editors automatically maximize when you focus them and they are in their minimized state. This feature is now working as before: Note: You can always maximize the active editor via View: Maximize Editor Group ( workbench.action.minimizeOtherEditors ) or reset all editor sizes via View: Reset Editor Group Sizes ( workbench.action.evenEditorWidths ).

View menu cleanup The View menu was growing very large and we decided to move many of the entries into a separate Appearance sub-menu to clean it up. Copy relative path VS Code always had an action to copy the absolute path of a file to the clipboard ( โŒ˜K โŒฅโŒ˜C (Windows Shift+Alt+C , Linux Ctrl+K Ctrl+Alt+C ) ). There is now a new action Copy Relative Path ( โŒ˜K โ‡งโŒฅโŒ˜C (Windows Ctrl+K Ctrl+Shift+C , Linux Ctrl+K Ctrl+Shift+Alt+C ) ) to copy the file path relative to the workspace folder root.

Note: You can get to this action from the context menu (for example, on a tab or a file in the File Explorer) by pressing and holding the Shift key ( Alt key on macOS) before opening the menu. Custom view: File resource decorations Custom views showing file resources will now have file decorations (Git, problems) shown. You can disable them using the settings explorer.decorations.colors and explorer.decorations.badges which disables them in File Explorer, Open Editors and Custom views.

Run npm scripts from package.json You can now run an npm script in a package.json file from the hover as shown below or from the context menu. Opening folder URIs You can now open an URI as a folder in VS Code, if there is an extension contributing a FileSystemProvider for that URI. We introduced a new command-line argument --folder-uri to do this. The following CLI command opens the VS Code GitHub repository as a folder, if you have RemoteHub extension installed. code --folder-uri remotehub://github.com/microsoft/vscode Rapid render On startup, the basic workbench layout is now restored much faster.

The restoration order is Activity Bar, Side Bar, and Status Bar, followed by headers and icons, and then the Explorer and editor region are populated. Rapid render is meant to improve perceived performance as the time you are looking at an empty canvas is reduced. We have more ideas how to improve rendering performance and we are interested in your feedback. Output panel VS Code's main, window, and shared processes each have their own logging channel, where you can now view the telemetry events sent when the log level is set to "Trace".

Data common to all telem

The rest of this page is on the live site.