[release] prepare v0.27.0 release

90fee6f CHANGELOG.md: v0.27.0
49e8caf release: adjust to create CHANGELOG.md early
930647a Revert "build: build dlv-dap@89ed5a0b"
76a9457 package.json: update gopls, dlv-dap versions
d1d61bc src/goInstallTools: pin dlv-dap version @ 89ed5a0b
80c1009 build: build dlv-dap@89ed5a0b
2a9fb96 src/welcome: mention that dlv-dap is the default debug adapter
a6066b7 docs: move dlv-dap to debugging, debugging to debugging-legacy
ed64853 src/goToolsInformation: update dlv-dap latest version
e66ec8d src/goDebugConfiguration: enable dlv-dap for local debugging
7502135 dlv-dap.md: use normal quotes
6658964 docs/dlv-dap.md: update remote debugging section
f2477e0 src/debugAdapter: send continued event on step requests
2e0c640 src/goMain: let go.locate.tools print tools versions
b9b3b47 README.md: encourage stackoverflow for Q&A
e6b8fe7 src/goInstallTools.ts: correct spacing in error message on Go not found
80c1b5c tools/relnotes: make some changes to generate release notes for gopls
2e8e703 src/goDebugConfiguration: dlv-dap doesn't expect 'wd'
15aaa8c src/goDebugFactory,src/goDebug: only add --log-output flag if --log is set
93a6e13 package.json: add go.terminal.activateEnvironment setting
29634d6 .github/workflows: add go1.17 rc1 in the long tests
b10aae5 src/config.ts: add Gitpod to the known cloud-based IDEs
805b29c src/goTest.ts: prompt for subtest name if there is no subtest at cursor
800dd70 tools: include script to help generate CHANGELOG
dee3427 docs: add minimum VS Code engine to troubleshooting guide
58226c9 src/goDebugConfiguration: always set cwd in attach mode & legacy adapter
72e205b docs/dlv-dap.md: update dlv-dap documentation
48418d4 test/integration/goDebug: enable set breakpoints while running tests
c3516da test/integration/goDebug: enable tests for delve flags
9b2405c test/integration/goDebug: enable tests skipped in dlv-dap mode
d0699a0 docs/dlv-dap: fix typos and errors in formatting
39d70a6 docs/dlv-dap: add features and images
a5d232d tools/generate: make debug property order deterministic
289a9ef docs/contributing.md: update docs to reflect npm version requirements
c6c97b9 tools/generate: generate debug configuration table
b2119e2 package.json: change version to v0.27.0-dev
689bf6f CHANGELOG.md: v0.26.0 change log & mention dlv-dap in README.md
dac1500 package.json: update debug configuration
7280045 tools/generate: simplify Properties parsing
2debbe8 .vscode/launch.json: Launch tools/generate
27bbf42 src/goToolsInformation: update dlv-dap@688f94a

Change-Id: I1771cc86d8c9e435e66b13da99931833536f1ae2
tree: fae85f6d1aab043c80fffa346a1ae42e7680ad4b
  1. .github/
  2. .vscode/
  3. build/
  4. docs/
  5. languages/
  6. media/
  7. snippets/
  8. src/
  9. syntaxes/
  10. test/
  11. third_party/
  12. tools/
  13. typings/
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.json
  17. .gitignore
  18. .prettierrc.js
  19. .prettierrc.json
  20. .vscodeignore
  21. CHANGELOG.md
  23. go.mod
  24. go.sum
  26. package-lock.json
  27. package.json
  28. README.md
  29. SECURITY.md
  30. tsconfig.json
  31. webpack.config.js

Go for Visual Studio Code


The VS Code Go extension provides rich language support for the Go programming language.

📣 Debugging using Delve's native DAP implementation is enabled by default in v0.27.0.

Quick Start

Welcome! 👋🏻
Whether you are new to Go or an experienced Go developer, we hope this extension fits your needs and enhances your development experience.

  • Step 1. If you haven't done so already, install Go and the VS Code Go extension.
  • Step 2. To activate the extension, open any directory or workspace containing Go code. Once activated, the Go status bar will appear in the bottom left corner of the window and show the recognized Go version.
  • Step 3. The extension depends on a set of extra command-line tools. If they are missing, the extension will show the “⚠️ Analysis Tools Missing” warning. Click the notification to complete the installation.

You are ready to Go :-)    🎉🎉🎉

Please be sure to learn more about the many features of this extension, as well as how to customize them. Take a look at Troubleshooting and Help for further guidance.

If you are new to Go, this article provides the overview on Go code organization and basic go commands. Watch “Getting started with VS Code Go” for an explanation of how to build your first Go application using VS Code Go.


This extension provides many features, including IntelliSense, code navigation, and code editing support. It also shows diagnostics as you work and provides enhanced support for testing and debugging your programs. See the full feature breakdown for more details and to learn how to tune its behavior.

In addition to integrated editing features, the extension provides several commands for working with Go files. You can access any of these by opening the Command Palette (Ctrl+Shift+P on Linux/Windows and Cmd+Shift+P on Mac), and then typing in the command name. See the full list of commands provided by this extension.

⚠️ Note: the default syntax highlighting for Go files is provided by a TextMate rule embedded in VS Code, not by this extension.


The extension uses a few command-line tools developed by the Go community. In particular, go, gopls, and dlv must be installed for this extension to work correctly. See the tools documentation for a complete list of tools the extension depends on.

In order to locate these command-line tools, the extension searches GOPATH/bin and directories specified in the PATH environment variable (or Path on Windows) with which the VS Code process has started. If the tools are not found, the extension will prompt you to install the missing tools and show the “⚠️ Analysis Tools Missing” warning in the bottom right corner. Please install them by responding to the warning notification, or by manually running the Go: Install/Update Tools command.

Setting up your workspace

Go modules are how Go manages dependencies in recent versions of Go. Modules replace the GOPATH-based approach to specifying which source files are used in a given build, and they are the default build mode in go1.16+. While this extension continues to support both Go modules and GOPATH modes, we highly recommend Go development in module mode. If you are working on existing projects, please consider migrating to modules.

Unlike the traditional GOPATH mode, module mode does not require the workspace to be located under GOPATH nor to use a specific structure. A module is defined by a directory tree of Go source files with a go.mod file in the tree's root directory.

Your project may involve one or more modules. If you are working with multiple modules or uncommon project layouts, you will need to configure your workspace by using Workspace Folders. Please see this documentation about supported workspace layouts.


The extension needs no configuration and should work out of the box. However, you may wish to adjust settings to customize its behavior. Please see the settings documentation for a comprehensive list of settings. See advanced topics for further customizations and unique use cases.


If the extension isn't working as you expect, you can take a look at our troubleshooting guides. There is one for general troubleshooting, and another specifically for troubleshooting the debugging feature.

Ask for help

If the troubleshooting guides did not resolve the issue, please reach out to us by filing an issue, starting a GitHub discussion, or by asking a question on Stack Overflow.

Also, you can take a look at learn.go.dev and golang.org/help for more general guidance on using Go.

Preview version

If you'd like to get early access to new features and bug fixes, you can use the nightly build of this extension. Learn how to install it in by reading the Go Nightly documentation.


We welcome your contributions and thank you for working to improve the Go development experience in VS Code. If you would like to help work on the VS Code Go extension, please see our contribution guide. It explains how to build and run the extension locally, and describes the process of sending a contribution.

Code of Conduct

This project follows the Go Community Code of Conduct. If you encounter a conduct-related issue, please mail conduct@golang.org.