軟體下載 VSCode 1.63.0

• 1

  版本確認

• 2

  檔案準備中

• 3

  檔案下載

What's new in this version:

VSCode 1.63.0
Fixed:
- Unable to run any tasks on a remote windows machine using openssh
- Google Japanese Input (IME) on Mac - Suggestions Overlap w/ Text
- Default settings deprecation warning with n breaks the json
- Asking for nvm to be installed, when it is already
- debug toolbar does not update if focused thread no longer exists
- Cannot type Korean. Splitted self or missing
- Zlib error: invalid distance too far back
- I cannot save a file when there is another file with longer name
- Call stack items aren't opening tabs with correct contents
- Emmet does not work in js/jsx files for VS Code 1.62.2(Universal)
- Perf: _removePropertiesWithPossibleUserInfo is ~10% of the cost of loading a renderer
- Perf: Update editor configuration only after extensions are registered
- vscode.dev can't switch branches in private repositories


VSCode 1.62.3
Fixed:
- Git operations fail due to empty VSCODE_GIT_ASKPASS_EXTRA_ARGS
- [json] editor stops validating: Invalid regular expression
- LanguageClient failing to initialize language server on 1.62.1
- Setting Sync: failed because of Unauthorized (401)


VSCode 1.62.2
Fixed:
- Always use a command line flag together with ELECTRON_RUN_AS_NODE
- Git operation hangs due to empty string in $GIT_ASKPASS
- Resolve shell environment failed on 1.62.1
- 1.62.1 - Sanity testing Mac server is failing
- WSL Extension instalation failure
- SetDecorations using contentText do not render on non ASCII lines
- Custom task problemMatcher results not appearing in problems panel when problem is on the first line
- Never prompted to select a kernel in Notebooks
- Semantic highlighting flickers on 1.62.0 and later
- Editors - pathsToEditors should ignore folders
- Crash on opening large files with bracket pair colorization
- Close Remote Connection blocked due to a veto from terminal


VSCode 1.62.1
The update addresses this security:
- Always use a command line flag together with ELECTRON_RUN_AS_NODE


VSCode 1.62.0
Visual Studio Code for the Web - vscode.dev (Preview):
- This iteration, we released a preview of Visual Studio Code for the Web. Visual Studio Code for the Web provides a zero-install experience running entirely in your browser, allowing you to quickly and safely browse source code repositories and make lightweight code changes. To get started, go to https://vscode.dev in your browser.
- VS Code for the Web has many of the features of VS Code desktop that you love, including search and syntax highlighting, along with extension support to work on your codebase. In addition to opening repositories, forks, and pull requests from source control providers like GitHub and Azure Repos, you can also work with code that is stored on your local machine.
- Not all extensions can run when VS Code is in the browser. Extensions that are purely declarative, such as themes, snippets, or grammars, can run unmodified in the browser. However, extensions that need to run code must be updated by the extension authors. We'd like to say thank you to the extension authors that already have published their extensions as web extensions.

Workbench:
Settings editor accessibility:
We made various Settings editor accessibility improvements:
- The Settings editor scrolls back to the top after performing a search, so the user does not end up midway through the search results after each search.
- The settings scope switcher is accessible via keyboard.
- Deprecated setting text blocks display an icon. Previously, the deprecated text was distinguished from the rest of the setting text only by color.
- More UI elements within the Settings editor have the setting ID as their name.

Updated search icons:
- The search icons are now the same weight and the match whole word icon was updated to be more distinguishable from the rest.

Parameter hint highlight:
- VS Code now highlights the current parameter in the parameter hint and the color can be themed via editorHoverWidget.highlightForeground

Editor:
Improved bracket pair guides:
- We continued iterating on bracket pair guides. Horizontal lines now outline the scope of a bracket pair. Also, vertical lines now depend on the indentation of the code that is surrounded by the bracket pair.
- Bracket pair guides can be enabled by setting editor.guides.bracketPairs to true (defaults to false). We added a third option "active" to only show a bracket pair guide for the active bracket pair.
- The new setting editor.guides.bracketPairsHorizontal controls if and when to render horizontal guides (defaults to active).
- New themable colors editorBracketPairGuide.background{1,...,6} and editorBracketPairGuide.activeBackground{1,...,6} can be used to customize the color of bracket pair guides

Customizable bracket pairs:
- You can now configure bracket pairs for a specific programming language through settings. editor.language.bracketPairs can be used to configure which bracket characters should be matched. If set, editor.language.colorizedBracketPairs independently configures which bracket pairs are colorized when bracket pair colorization or bracket pair guides are enabled.

Display hovers above or below the current line:
- You can now choose between displaying IntelliSense hovers above (default) or below the current line. By setting editor.hover.above to false, hovers will render below the current line.

Unicode directional formatting characters:
- To address CVE-2021-42574, VS Code now renders Unicode directional formatting characters by default. Consider the following text snippet.
- The above text snippet contains two explicit directional formatting characters, U+202E (RIGHT-TO-LEFT OVERRIDE) and U+202C (POP DIRECTIONAL FORMATTING). These characters can influence Unicode's Bidirectional Algorithm and could be used to craft source code that renders differently than what compilers would execute.
- The special rendering of these directional formatting characters can be turned off by setting editor.renderControlCharacters to false. The setting editor.renderControlCharacters is now true by default.

Extensions:
Verified extension publishers:
- VS Code now shows if the domains of an extension publisher are verified by the Visual Studio Marketplace
- If you are an extension author, more details about how to become a verified publisher can be found in the Publishing Extensions topic

Terminal:
New default keybindings for special characters:
- The following keybindings were added that are typically supported in other terminals:
- ctrl+shift+2: Inputs the null character (0x00).
- ctrl+shift+6: Inputs the record separator character (0x1E).
- ctrl+/: Inputs the unit separator character (0x1F).

Languages:
- Configure how HTML completes attributes:
- There is a new setting html.completion.attributeDefaultValue that lets you choose how values are filled in when an HTML attribute is completed:
- doublequotes: The value is placed in double quotes (default)
- singlequotes: The value is placed in single quotes
- empty: The value is left empty

Emmet improvements:
- The new Emmet: Update Tag command (editor.emmet.action.updateTag) updates the placeholder with the HTML tag to be updated.
- The extension also activates now when one tries to run any Emmet command. This change should fix an issue where some commands were not found when run from the Command Palette, while also keeping the activation event list more precise so that Emmet does not start up unnecessarily, such as in an empty workspace.
- For multi-root workspaces, Emmet now sources snippets from all workspace folders, rather than just the first one. As a result, custom snippets from all workspace folders will be suggested when editing an applicable file in the workspace.

Notebooks:
Find and Replace supports capturing groups:
- The Find and Replace widget in the notebook editor now supports regular expression capturing groups
- In the short video below, replace uses the first (and only) captured text ('a')

Better selection of output renderers and mimetypes:
- Notebook cells can output multiple types of data (mimetypes) that can be rendered in different ways both by VS Code itself and extensions. Previously, VS Code had basic memoization (caching) of the selected renderer for a mimetype, and you could manually configure your preferred mimetypes using the notebook.displayOrder setting. However, VS Code wasn't particularly smart about picking the best renderer for a mimetype, and preferred mimetypes had to be updated manually.
- Now, preferred renderers are cached on a per-notebook type, level in the workspace. Additionally, if you switch to view a different mimetype, that preference will be updated in-memory for the VS Code session, and you can use the Notebook: Save Mimetype Display Order command to easily update the notebook.displayOrder setting to the working preference.

Contributions to extensions:
Jupyter:
- Kernels
- In order to make it easier to identify kernels, the Jupyter extension now groups kernels in the kernel picker.
- You can now filter the list of kernels displayed in the kernel picker, either globally or on a workspace basis. This is helpful if you have a large number of kernels installed but usually only work with a subset.
- To manage the list of kernels displayed, you can use the command Jupyter: Filter Kernels from the Command Palette.

Interactive Window:
- Automatic cell creation when running the last cells in an Interactive Window using Shift+Enter can now be configured via the setting jupyter.newCellOnRunLast. If you don't want the default behavior to add a new cell, you can set jupyter.netCellOnRunLast to false.

ESLint:
- A new version of the ESLint extension has shipped. Major improvements are:
- Extended support for ESLint version 8.x.
- The ability to define the rule set that is applied during code action on save and format via the setting eslint.codeActionsOnSave.rules.

GitHub Pull Requests and Issues:
- Work continues on the GitHub Pull Requests and Issues extension, which allows you to work on, create, and manage pull requests and issues. Check out the changelog for the 0.32.0 release of the extension to see the highlights.

Remote Development:
- Work continues on the Remote Development extensions, which allow you to use a container, remote machine, or the Windows Subsystem for Linux (WSL) as a full-featured development environment.

Feature highlights in 1.62 include:
- New setting remote.SSH.foldersSortOrder to sort SSH targets alphabetically or by recent use.
- Windows Subsystem for Linux indicator lets you quickly know whether you are using WSL 1 or WSL 2.
- Advanced container configuration videos covering how to persist bash history and work with monorepos.

Preview features:
TypeScript 4.5 support:
This update adds support for the upcoming TypeScript 4.5 release. The TypeScript 4.5 beta announcement post has more information about the new language and tooling features. Some tooling highlights:
- Method signature completions.
- JSX attribute completions.
- More accurate reference counts for the references CodeLens.
- To start using the TypeScript 4.5 nightly builds, install the TypeScript Nightly extension.
- Please share your feedback and let us know if you run into any bugs with TypeScript 4.5.
- Extension authoring:
- Emoji support in file decorations
- The file decorations API now supports emojis as badge texts.

MarkdownString.supportHtml:
- The new supportHtml property on MarkdownString enables rendering of a safe subset of raw HTML that appears inside the Markdown text.
- The supportHtml property defaults to false. When disabled, VS Code will strip out any raw HTML tags that appear in the Markdown text.

Engineering:
File watching changes:
- File watching in VS Code changed to a new library, thanks to the work of the Parcel team with their @parcel/watcher. We will gradually roll out this change to all users in the upcoming weeks. Linux users will be happy to learn that the files.watcherExclude now applies natively so that the number of file handles VS Code needs open for file watching can be greatly reduced.
- The existing files.legacyWatcher setting was changed to an enumeration with these values:
- on - The new file watcher will never be used.
- off - The new file watcher will always be used.
- default - The new file watcher will only be used when you open multi-root workspaces (via a .code-workspace file).
- You should not notice any difference in your day to day work, but if file watching is broken for you, please report an issue.

Progress for Electron sandbox support:
- As we continue to make the VS Code workbench ready for enabling Electron's sandbox, we made progress on moving Node.js file services out of the workbench window into a different process. The same is true for the file watcher that no longer forks from the workbench window, but from a background process. This change is enabled by default in VS Code Insiders and will be the default in Stable for our November release.

Notable fixes:
- 73061: Enumerable properties mixed with regular properties
- 130868: Emmet suggestions list missing entries after adding custom snippets.json
- 131966: Emmet unable to expand abbreviation with onclick attribute
- 135110: Support different border settings for vertical or horizontal layouts, for in-group editor splitting


VSCode 1.61.2
The update addresses these issues:
- Web: Handles may contain slashes at the end
- Focus of commit message textbox swaps when files are changed meanwhile


VSCode 1.61.1
Fixed:
- Process handles leaked by pty host on windows
- September 2021 Recovery Endgame
- High CPU Usage: Every VS Code window eats 5+% CPU, even idle, even in the background
- Empty HoverWidget is visible at startup
- New Telemetry Level should respect my prior settings
- Source Control bug when creating or changing branch in the workspace


VSCode 1.61.0
- Split editors within the same group - Quickly create side-by-side editors for the same file
- Locked editor groups - Select editor types to automatically lock in an editor group
- Better display of deleted and readonly files - Tab decorations highlight deleted and readonly files
- Bracket pair guides - Display vertical guides to link matching bracket pairs
- Fixed terminal dimensions - Set an active terminal's width and height
- Jupyter Notebook improvements - Table of Contents view, full debugging support
- Platform-specific extensions - Publish different extension versions for Windows, macOS, and Linux
- Virtual Workspaces extension guide - Learn how to update your extension for virtual environments
- Advanced container configuration - Tips, code samples, and videos to help configure development containers


VSCode 1.60.2
The update addresses these issues:
- The GitHub.codespaces extension gets activated twice when creating a new codespace
- Bundle TS 4.4.3
- ugust 2021 Endgame Recovery 2 endgame-plan
- Codespaces: Debugging is broken
- Automatic language detection overrides openTextDocument API language parameter
- Undo stops working after focusing webview


VSCode 1.60.1
Fixed:
- npm script not work in default terminal
- Context menu command "Open in Integrated Terminal" does not use Default Profile
- Go to Symbol in Workspace
- Allow also setting the language_info in a notebook
- Show Log from Container Creation Progress notification has no effect
- SSH Remote fails to connect
- Inline-suggestion appearing at previous cursor location
- August 2021 Endgame Recovery
- v1.60: "Auto language select" feature sets "CoffeeScript" language in "Git commit" files
- Powershell console opens every time I launch VS Code with a project
- Unable to save notebook when executing a long running cell


VSCode 1.60.0
- Automatic language detection - Programming language detected when you paste into VS Code
- Built-in fast bracket colorization - Fast bracket matching and colorization for large files
- Settings editor syntax highlighting - Rich syntax highlighting for setting description code blocks
- Custom terminal glyph rendering - Better display of box drawing and block element characters
- Set debugging Watch values - Change watched values during a debugging session
- Notebook improvements - Markdown link navigation, faster rendering of large outputs
- JavaScript/TypeScript inlay hints - Inline hints for parameter names and types, and more
- Locked editor group preview - Keep a preferred editor layout by locking the editor group
- Python extension testing updates - Better support for test discovery, navigation, and status
- Web extension authors guide - Learn how to update your extension for VS Code in the browser


VSCode 1.59.1
Fixed:
- Notebooks cannot be opened on 1.59
- Authentication decryption error
- tasks.onDidEndTaskProcess is called too many times in VS Code v1.59
- Perma-hang/crash on M1 MBP with universal build
- July 2021 Endgame Recovery
- Stdout generated raw data file not in expected format.
- Typing repeated dots in js expands to first suggestion


VSCode 1.59.0
- 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
- Remote - Containers devcontainer CLI - Command line interface for working with development containers


VSCode 1.58.2
Fixed:
- June 2021 Endgame Recovery 2
- Only acquire workspace storage locks on the remote extension host
- Remote extension will not work if it depends on a local UI one
- Terminal is tiny when extensions create and show them
- When multiple ghost text parts have line breaks, the first line of the ghost text gets deleted
- Using command line to open vscode causes code warning
- Trust and Continue dialog need two clicks on Continue to go away
- VS Code Terminal doesn't autofocus
- MacOS: Could not move terminal into editor area after first move


VSCode 1.58.1
The update addresses these security issues:
- Improves Git security with untrusted workspaces bug git important
- Don't use guessable nonces in webview
- Update distro hash


VSCode 1.58.0
- Terminals in the editor - Create or move terminals into the editor area
- Workspace Trust - Quickly customize Workspace Trust settings, disable Restricted Mode banner
- Editor scroll bar customization - Set bar visibility and width, click navigation behavior
- Markdown preview KaTeX support - Math support in the Markdown preview
- Settings editor improvements - Support for multiple checkboxes and enumeration dropdowns
- Sticky debug environment choice - Debugger remembers your previous environment choice
- Jupyter Interactive window - Run Jupyter code directly in an interactive window
- Jupyter notebook debugging - Debug Jupyter notebook code from within VS Code
- 'Open in VS Code' badge - Lets visitors quickly open your GitHub repo in VS Code
- Data Science tutorials - Learn about Jupyter Notebooks, PyTorch, and more
VSCode 1.57.1
- May 2021 Endgame Recovery
- Scrolling on mouse click
- macOS: restore Cmd+W closing the window when all tabs are closed
- 1.57.0 (macOS): window behaves different now (fullscreen & priority issues)
- "Open New External Terminal" doesn't work if no terminal settings are present
- Entire settings file got erased on new latest update. Just FYI


VSCode 1.57.0
- Workspace Trust - Extra security against code execution when browsing unfamiliar source code
- New Getting Started experience - Helps you quickly set up and learn about VS Code
- Remote Repositories - Browse and edit code without locally cloning repositories
- Terminal tabs - Tabs let you easily create, manage, and group multiple open terminals
- Edge browser debugging - Integrates the Microsoft Edge Developer Tools directly into VS Code
- JSDoc @link support - Add @link tags in your comments for fast symbol navigation
- Go to Definition for non-code files - Quickly jump to images and stylesheets
- Notebook API finalized - Notebook API for native notebook support in VS Code
- VS Code at Build 2021 blog post - Catch up with on-demand sessions featuring VS Code


VSCode 1.56.2
- C# syntax highlighting incorrect in 1.56
- Use shell/shellArgs over defaultProfile if specified
- HTML files now require an extension to run
- The default Monokai highlight color is displayed incorrectly
- No longer scaling toolbar icon
- On PC 'Delete' key not working on insiders for approx last week
- Version control icons became minuscule with latest update


VSCode 1.56.1
The update addresses these security issues:
- Do not invoke resolveWithInteraction over terminal settings
- Change grunt, gulp and jake task auto detection to be off by default


VSCode 1.56.0
- Improved hover feedback - Helps you quickly find clickable editor actions
- Terminal profile improvements - Create a custom default terminal profile
- Debugger inline values - Display variable values inline during debugging sessions
- Notebook KaTeX support - Math support in notebook Markdown cells
- Remote - Containers volumes view - Manage mounted volumes within Docker containers
- winget installation - VS Code is available via the Windows Package Manager
- New introductory videos - Videos for getting started with VS Code as well as working with C++
- Terminal tabs preview - Get a first look at managing open terminals with the new tabs view


VSCode 1.55.2
The update addresses these security issues:
- Limit set of allowed remote CLI commands bug important
- command: links should be only selectively enabled bug important
- Spawning php should use its complete disk path bug important
- Spawning npm should use its complete disk path bug important
- CSS should use variables when using editor.fontFamily bug important
- The http.proxy setting should use machine or application scope bug important


VSCode 1.55.1
- Proxy agent is hijacking requests and redirecting them to localhost
- Remote extensions are not installed automatically from devcontainer.json
- Bug Sur icons glitched on non-hidpi screens
- ECONNREFUSED debugging browsers in WSL2


VSCode 1.55.0
- Accessibility improvements - Multi-cursor support and increased line limit
- Updated icons for macOS Big Sur - Brand icons that match the visual style of Big Sur
- Improvements to breakpoints - Inline breakpoints menu, and more
- Editor status decorations - Editor tab status decorations are on by default
- Customize keyboard shortcuts editor - Resize columns in the keyboard shortcuts editor
- Improved remote ports management - Port forwarding autodetection, regex naming, and more
- Terminal profiles - Define profiles in terminal to conveniently launch non-default shells
- Notebook improvements - Multiple cell selection, and more customizable diff editor
- VS Code on Raspberry Pi - New topic explaining how to install VS Code on Raspberry Pi devices


VSCode 1.54.3
- February Recovery 3
- VS Code is unable to activate a debugger extension because of path casing discrepancies


VSCode 1.54.2
Fixed:
- Listener leak in Ports view
- Close terminal warning shows even if no terminal is open
- Command "View: Join all editor groups" not working after update
- Pick up TS 4.2.3
- Cannot find module 'worker_threads' using js debugger auto attach
- Completed tiles of "Getting Started" don't reopen
- List focus background needs proper migration
- Renaming a folder adds it to history
- FileSystemProvider extension: throwing a FileSystemError in readFile does not report to user
- Hide pty host unresponsive notification when it becomes responsive again
- Terminal pty host unresponsive after closing a VS Code window
- Prevent env var relaunch from extension owned terminals


VSCode 1.54.1
- The update addresses an issue with an extension dependency


VSCode 1.53.2
Fixed:
- TS Server fatal error: Cannot read property 'indexOf' of undefined
- <> in all files
- Minimap keeps disappearing
- Fresh install won't open any windows or allow me to open any windows
- First call to activeDebugConsole.appendLine() while debugging JavaScript doesn't appear in the debug console
- Cannot unset StatusBarItem background from errorBackground
- tasks.json npm script does not work with arguments since 1.53
- v1.53 creates debug.log automatically
- The default extension for untitled files is not .txt
- Emmet suggestions bug in SASS files
- VSCode emmet SASS snippets
- IME ON at Alt+` key, Focus ALT Menu


VSCode 1.53.1
Security issues:
- Bundle TypeScript 4.1.4
- Dragging files from explorer to terminal may execute a command
- Pick up new distro version and bump version


VSCode 1.53.0
- Wrap tabs - Wrap editor tabs in the workbench instead of having a scrollbar
- Configure tab decorations - Add editor tab status decorations
- Customize search mode - Use the Search view or open a new Search editor
- JavaScript debugging - Support for conditional exception breakpoints and Node.js worker_threads
- Notebook UX updates - Outline view for Notebook cells, and breadcrumbs for improved navigation
- Markdown preview image auto update - Preview automatically updates when images change
- Emmet improvements - Faster performance and supporting the latest features
- Extension guidelines - Documented best practices for extension authors
- Remote Development video series - Learn to create and configure container-based environments


VSCode 1.52.1
- November 2020 Recovery Endgame
- Check for all possible localhost string when checking if a tunnel already exists
- Can not set breakpoint in PHP files
- notebook status bar icon colors missing