[release] prepare v0.26.0 release

1bc09d8 src/goDebugConfiguration: resolve relative paths used in cwd, output, program
ac7b209 package-lock.json: npm audit fix
4574878 package.json: pick up gopls@v0.7.0 settings and update tools version
7ea6b76 src/goDebugConfiguration: default to dlv-dap in preview mode
e7e25d2 Revert ".github/workflows: use 'stable' version for release-nightly"
570a0a4 src/goModules.ts: open go.mod after init
936ecdf .github/workflows: use 'stable' version for release-nightly
a1d1329 src/goImport: use gopls methods to list and add contextual imports
03a8315 src/goDebugFactory.ts: fix problem with attach requests
82d2b5d src/goTest: Add command Test Function At Cursor or Test Previous
505ad8d build/all.bash: use go install for tool installation
e7c91ef package-lock.json: npm audit fix
616928d .github/workflows: use tmp dir as working dir when installing tools
ab4f21a src/goDebugConfiguration: let vscode resolve pick process
ecf30b7 src/goLanguageServer: migrate opt-out survey to Qualtrics
4cb78f6 src/goLint: handle the case where no editor is active
c5070dc CHANGELOG.md: v0.25.1 updates
b79bdf9 test/integration/goDebug.test.ts: include the debugger logging in tests
9b2b1ef src/goToolsInformation: update dlv-dap version
d88ee9b src/goDebugFactory: respond with error if dlv dap failed to start
fe7b40b src/goEnvironmentStatus: avoid TypeError for notification closed without action
f22b65a src/goLint: fix type error caused by a bug in goLint
b6a3630 src/goDebugFactory: connect after createDebugAdapterDescriptor
cbdd328 src/goSurvey: double survey probability and send half to v2 survey
4510773 src/goSurvey: increase the prompt probability to 0.03
ad1dcce test/integration/goDebug.test.ts: accept 'exception' as stopped reason
c54f5e6 package.json: set virtualWorkspaces capability to false
9fa871b src/goMain: warn users if go.goroot is set
0f4b38f tools/generate.go: update gopls and dlv-dap versions in generate
39445e1 src/goDebugConfiguration: use fileWorkspaceFolder in multi root workspace
961ab1c src/goLogging: fix the default logger
646faec package.json: use the updated workspace trust API
e8dc6c4 package.json: remove 'init' debug attribute
b9f1961 [release] Update CHANGELOG
64592bc src/debugAdapter: default path separator to '/'
a2c2efc package.json: bump dev version number to 0.26.0-dev
7340877 [release] Update CHANGELOG for v0.25.0
4bae281 src/goDebugConfiguration.ts: add substitutePath to go.delveConfig
d9fd8f0 docs: update dlv-dap.md
cea0269 test/integration/goDebug: wait for debug adapter dispose in teardown test
41c5ee9 test/integration/goDebug.test.ts: use dc.on to wait for output event
50efa73 test/integration/goDebug: modify teardown+cleanup test
8803f91 docs: update outdated lint tool documentation in features.md
6571316 .github/workflows: move dlv to dlv-dap before getting dlv again
54986cd docs/settings.md: update gopls settings

Change-Id: I6df1e8bbd836573b243fa9f290a149bc56d985a3
tree: 4fc9b890795f9346c8c9b757bcf9a5d4b054deb0
  1. .editorconfig
  2. .eslintignore
  3. .eslintrc.json
  4. .github/
  5. .gitignore
  6. .prettierrc.js
  7. .prettierrc.json
  8. .vscode/
  9. .vscodeignore
  10. CHANGELOG.md
  13. README.md
  14. SECURITY.md
  15. build/
  16. docs/
  17. go.mod
  18. languages/
  19. media/
  20. package-lock.json
  21. package.json
  22. snippets/
  23. src/
  24. syntaxes/
  25. test/
  26. third_party/
  27. tools/
  28. tsconfig.json
  29. typings/
  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.