[release] prepare v0.37.0 release

7df32c8f CHANGELOG.md: addresses comments from cl/457476
f820eaef CHANGELOG.md: change log for v0.37.0
107463e2 package-lock.json: npm audit fix
2f29f891 src/welcome: vulncheck analyzer announcement for v0.37.0
d28aeac9 src/goTest: add codelens for sub tests
357391a3 docs/features: add vulncheck feature description
a64573f3 src/goVulncheck: add the feedback link, polish govulncheck output
6c62e5d1 src/goVulncheck: add go.vulncheck.toggle command
087370a3 goplsSurvey: remove lumpiness in survey days
c141ad80 package.json: add 'go.diagnostic.vulncheck'
7848fb37 src/goVulncheck: add vulncheck output links provider
b2decd20 src/goVulncheck2: rename goVulncheck2.ts to goVulncheck.ts
c40f0734 src/goVulncheck: remove the experimental "Go: Run Vulncheck" command
8ffb271d syntaxes: color govulncheck output in the output channel
3bcbaafd src/goVulncheck2: output govulncheck progress and result
aff24c55 test/unit/goDebug: delete the goDebug test
35966351 package.json: sync gopls settings (gopls@v0.11.0-pre.1)
34c0efbd src/goDebugFactory: re-enable version check
800c2331 src/goVulncheck: update gopls govulncheck command name
f76aad62 src/context: add govulncheckOutputChannel
3a4f19df src/debugAdapter: fix typo in panic message
5be77168 .github/workflows: update node version to 18
e51a4d72 src/goEnvironment: make the window reload request visible
1da1ea2c package-lock.json: bump loader-utils from 1.4.0 to 1.4.1
28f7c073 src/goInstallTools: handle unknown tools
8f81613e docs/settings: make the custom formatter support more visible
752577ea test/gopls: narrow the scope of fake formatTool setting
b713787d docs/features: mention inlay hints and update diagnostics part
b54d132c .github/workflows/wiki: use cp instead of diff to handle binaries
f67d75f6 src/goCover: ignore bogus-looking line/column data
91fe72d9 package.json: start of v0.37.0 dev
12dabf30 tools/license.sh: add CC-BY-4.0 license

Change-Id: I89299b79b7939a759f875073baeedad6c6b8e346
tree: 126eb2f141fbdc7c2105af21b3eb34fab687fe54
  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.

📣 Remote attach debugging is now available via Delve's native DAP implementation with Delve v1.7.3 or newer. It enchances remote debugging with the same debugging features that are already in use for local debugging. It is now the default with the Go Nightly build of the extension and will become the default for the stable releases in mid 2022. We recommend switching your remote attach configurations in launch.json to use "debugAdapter":"dlv-dap" now to verify that this works for you. Please file a new issue if you encounter any problems.

📣📣 Watch Debugging Treasure Hunt from GopherCon 2021 for a fun take on a debugging demo with VS Code Go and Delve DAP.

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.14 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.


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.