[release] prepare v0.24.1 release

ec040a9 .github/release_plan.md: add a template for the release plan
ce52d04 src/goTools: update dlv-dap latest version
18e3636 package.json: sync gopls settings to match v0.6.10
4948401 src/goDebugFactory.ts: send terminated event on server start error
6f9c0eb docs/dlv-dap.md: include go.delveConfig setting for debugAdapter
337ae93 src/testUtils: tighten test function detection regex
bded07b src/goDebugConfiguration.ts: clean up launch.json quickpick
c189ec0 src/goTest.ts: allow users to select default debug adapter
d5c8951 test/integration/goDebug: enable noDebug tests for dlv dap
44b7d36 src/goDebugConfiguration: clean up launch config snippets
d6e513e src/goDebugFactory.ts: fix output event destination
1d549a2 src/goInstallTools: linkify dlv-dap installation instruction
1cacf9d docs/dlv-dap: add the link to the list of dlv-dap only features
66b684a test/integration/goDebug.test.ts: add test for runtime error
25d2981 CHANGELOG.md: for v0.24.0
d7f3a5a package.json/package-lock.json: update dev version
505f363 src/goTools: update latest version of dlv-dap
8e70c58 src/goInstallTools.ts: update install instructions for dlv-dap
33339e6 test/integration/goDebug.test.ts: remove '.only' from test
d1ca321 test/integration/goDebug.test.ts: enable switch goroutine test dap
d9fca4d src/goInstallTools: remove dlv-dap from missing tools
f56b715 src/goDebugFactory: output dlv dap command as console output event
471ed7e test/integration: use DelveDAPOutputAdapter in dlv-dap mode testing
f8f5433 src/goDebugFactory: wait before killing the spawned dap server
e545b83 test/integration: disable broken tests
afbc36c .github/workflows: correct lint check condition
42de993 docs/dlv-dap: update installation instruction

Change-Id: I0ad0961a4980471cd2d20cb1c5d959a06f612ef8
tree: 43d2f9d573de4e067d81ac0f124764b877d776d3
  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
  25. package-lock.json
  26. package.json
  27. README.md
  28. SECURITY.md
  29. tsconfig.json
  30. webpack.config.js

Go for Visual Studio Code


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

📣 Gopls, the official Go language server, is now enabled in VS Code by default. Gopls replaces several legacy tools to provide IDE features while editing Go code. See issue 1037 for more information.

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 in the Gophers Slack. We hang out in the #vscode channel!

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.