[release] prepare v0.40.1 release

7a5c1bb9 CHANGELOG.md: address suzmue's comment and apply style fixes
f17266ed CHANGELOG.md: change log for v0.40.1
c37e0fed package-lock.json: run npm audit fix
35ca87eb src/goExplorer: add GOTOOLCHAIN in the go env var explorer
077c2366 go.mod: update dependencies to silence vuln reports
3888cc49 src/goTest: fix display pprof result page when using ssh
ec9e90d7 src/goToolsInformation: set min go version for golangci-lint
34f54ac4 package.json: update vscode test electron dependency
39008949 go.mod: go mod tidy -go=1.18
d6fb2028 src/goTest: fix bugs in subtest handling
fae8cb91 src/goMain: stop trying to diagnose when gopls is not running
308c6c02 src/language/goLanguageServer: fix parameter hint setting query
322014f6 src/utils/pathUtils: adjust snap go path
4316a961 src/language/goLanguageServer: improve suggestGoplsIssueReport
d8333230 package.json: remove 'workspaceContains' from activation events
07bea226 docs/contributing.md: remove unnecessary quote
455b799b test/integration: delete legacy DA's path mapping tests
ffde5a1b test/runTest: suppress vscode download log
95a552b5 package.json: update @vscode/test-electron to 2.3.6
7f843ca3 src/welcome: delete unused variables
c6bfee8f .github/workflows: upgrade to v4 github actions
e864a1ef package.json: start the v0.41.0-dev cycle
8190ad68 CHANGELOG.md: fix delve version used in v0.40.0 release
ed92a0c2 CHANGELOG.md: update planned release date
f76ac356 tools: add max version for delve

Change-Id: I26e97fabb61ebd80954fe78c204066ffd092f9b5
tree: 8dea554ddfa501711201288920f2c258d27fb5c5
  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. codereview.cfg
  24. go.mod
  25. go.sum
  27. package-lock.json
  28. package.json
  29. README.md
  30. SECURITY.md
  31. tsconfig.json

Go for Visual Studio Code


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


  • Visual Studio Code 1.75 or newer (or editors compatible with VS Code 1.75+ APIs)
  • Go 1.18 or newer

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.

  1. Install Go 1.18 or newer if you haven't already.

  2. Install the VS Code Go extension.

  3. Open any directory or workspace containing Go code to automatically activate the extension. The Go status bar appears in the bottom left corner of the window and displays your Go version.

  4. The extension depends on go, gopls, dlv and other optional tools. If any of the dependencies are missing, the ⚠️ Analysis Tools Missing warning is displayed. Click on the warning to download dependencies.

    See the tools documentation for a complete list of tools the extension depends on.

You are ready to Go :-)    🎉🎉🎉

What's next

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.

Feature highlights

  • IntelliSense - Results appear for symbols as you type.
  • Code navigation - Jump to or peek at a symbol's declaration.
  • Code editing - Support for saved snippets, formatting and code organization, and automatic organization of imports.
  • Diagnostics - Build, vet, and lint errors shown as you type or on save.
  • Enhanced support for testing and debugging

See the full feature breakdown for more details.

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.

For better syntax highlighting, we recommend enabling semantic highlighting by turning on Gopls' ui.semanticTokens setting. "gopls": { "ui.semanticTokens": true }

Setting up your workspace

The VS Code Go extension supports both GOPATH and Go modules modes.

Go modules are used to manage 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+. 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. See the Supported workspace layouts documentation for more information.

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.


VS Code Go extension relies on the Go Telemetry to learn insights about the performance and stability of the extension and the language server (`gopls``). Go Telemetry data uploading is disabled by default and can be enabled with the following command:

go run golang.org/x/telemetry/cmd/gotelemetry@latest on

After telemetry is enabled, the language server will upload metrics and stack traces to telemetry.go.dev. You can inspect what data is collected and can be uploaded by running:

go run golang.org/x/telemetry/cmdgotelemetry@latest view

If we get enough adoption, this data can significantly advance the pace of the Go extension development, and help us meet a higher standard of reliability. For example:

  • Even with semi-automated crash reports in VS Code, we've seen several crashers go unreported for weeks or months.
  • Even with a suite of benchmarks, some performance regressions don't show up in our benchmark environment (such as the completion bug mentioned below!).
  • Even with lots of great ideas for how to improve gopls, we have limited resources. Telemetry can help us identify which new features are most important, and which existing features aren‘t being used or aren’t working well.

These are just a few ways that telemetry can improve gopls. The telemetry blog post series contains many more.

Go telemetry is designed to be transparent and privacy-preserving. If you have concerns about enabling telemetry, you can learn more at https://telemetry.go.dev/privacy.


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, see our contribution guide to learn how to build and run the VS Code Go extension locally and contribute to the project.

Code of Conduct

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