GoLand
 
2021.3
Shortcuts: Windows
Get GoLand
You are viewing the documentation for an earlier version of GoLand.
  1. Project configuration
  2. Projects
  3. Create a new project
  4. Go

Go

Last modified: 19 March 2022

By default, GoLand suggests creating a Go modules project. With Go modules, you do not need to keep your project files under GOPATH and can easily manage dependencies in your project. Read more about Go modules at blog.golang.org.

Create a project with Go modules integration

  1. Select File | New | Project.

  2. In the New Project page, select Go.

  3. In the Location field, specify the path where you want to store your project.

  4. In the GOROOT field, specify the location of your Go installation. Usually, the location is defined automatically.

    To change or install a new version of Go SDK, click the Add SDK… button and select Local… to choose the Go SDK version on your hard drive, or select Download… to download Go SDK from the official repository. For more information about installing Go SDK, see Installing Go SDK.

  5. In the Environment field, specify environment variables that you need for your project. For example, the GOPROXY environment variable. Read more about environment variables in the Environment variables section.

  6. (Optional) To use vendoring mode, select the Enable vendoring support automatically checkbox. Note that automatic vendoring mode became a built-in Go feature in Go 1.14 RC. But you can configure this setting for earlier Go versions. For more information about vendoring, see Vendoring.

  7. Click Create.

    Integration with Go

Working with Go modules

In the Project tool window (View | Tool Windows | Project), Go modules are displayed with their full import path. The version of each Go Module is shown in a dimmed font color to help you distinguish between them.

o Module is shown in a dimmed font color

If you create a new Go modules project in the IDE, Go modules are already enabled. If you pulled your Go modules project from Github, you need to enable Go modules manually.

Enable Go in a project

  1. Open settings by pressing Ctrl+Alt+S and navigate to Go | Go.

  2. Select the Enable Go modules integration checkbox.

  3. Click OK.

    Enable Go in a project

Working with dependencies

To work with dependencies, you can select between the following options:

  • Sync dependencies: fetches and downloads missed dependencies and removes unused ones by calling go mod tidy/vendor. In replace directives, the IDE would not download or delete missed dependencies, and the lines with these unused dependencies would be marked red. It is not an error and does not affect how the application works.

  • Download all modules to the module cache: fetches and downloads all the dependencies and places them under the External Libraries in the Project tool window (View | Tool Windows | Project).

  • Download <module_name> to the module cache: fetch and download the selected module and place it under the External Libraries in the Project tool window (View | Tool Windows | Project).

Download all modules to the module cache

Synchronize dependencies from the opened Go file

  1. Ensure that Go modules integration is enabled. For more information about enabling Go modules integration, see Enable Go in a project.

  2. Click a dependency in the import section, press Alt+Enter and select Sync dependencies.

    Fetch dependencies

Synchronize dependencies from go.mod

You can fetch missed dependencies and remove unused dependencies.

  1. Ensure that Go modules integration is enabled. For more information about enabling Go modules integration, see Enable Go in a project.

  2. In the Project tool window (View | Tool Windows | Project), double-click the MOD file.

  3. Click a dependency declaration.

  4. Press Alt+Enter and select Sync dependencies.

    Fetch a source with Go

note

If you remove a dependency from the go.mod file, GoLand automatically removes the dependency from the list of available libraries.

Configure automatic run of 'go list' for 'go.mod'

By default, GoLand would automatically run go list commands after every modification of go.mod. You can control this behavior by configuring the Reload project after changes in the build scripts option.

Configuration for running 'go list'

  1. Open settings by pressing Ctrl+Alt+S and navigate to Build, Execution, Deployment | Build Tools.

  2. You can set the following options depending on your workflow:

    • Any changes: run go list after any modification of go.mod.

    • External changes: do not run go list automatically when you edit the file inside the IDE. After you finished editing files in the IDE, click the Load Go modules Changes icon (the Load Go modules Changes icon) to apply and load your changes.

      Load Go modules Changes icon

    • If you do not want to run go list after every modification of go.mod, clear the Reload project after changes in the build scripts checkbox.

      If the checkbox is cleared, you will see the Load Go modules Changes icon on all types of changes: external and internal.

Create a diagram of dependencies

The go.mod file lists dependencies for your project. You can use this file to build a diagram of dependencies.

Before you begin, ensure that your project is under GOROOT.

  1. Enable Go in your project.

  2. Right-click the go.mod file in your project and select Diagrams | Show Diagram.

    https://resources.jetbrains.com/help/img/idea/2021.3/go_show_dependency_diagram.png
    Gif

Toggle vendoring mode

You can toggle vendoring mode in Go versions 1.13 and earlier. In Go 1.14 RC, automatic vendoring mode became a built-in Go feature.

  1. Open settings by pressing Ctrl+Alt+S and navigate to Go | GOROOT.

  2. From the GOROOT list, select the Go version 1.13 or earlier.

  3. Click the Go menu item.

  4. Clear or select the Enable vendoring support automatically checkbox and click OK.

    Automatic vendoring mode in Go 1.13 and earlier versions

note

Starting from Go 1.14 RC, GoLand also enables automatic vendoring mode by default. You cannot disable this setting. Read more about vendoring in Vendoring.

Navigate from a dependency import path to package source files

  1. In the Project tool window (View | Tool Windows | Project), double-click the go.mod file.

  2. Click the last element of a dependency import path and click Navigate | Declaration or Usages Ctrl+B. For example, if the import path is github.com/gorilla/mux, click on mux.

    Navigate from a dependency import path to package source files

Environment variables

Environment variables provide a way to set application execution parameters. Environment variables can store addresses of proxy servers that you want to use to download dependencies (GOPROXY), names of packages that are considered private (GOPRIVATE), and other values. In GoLand, you can use the following templates for environment variables:

  • GOPROXY: defines proxy servers that must be used to download dependencies. These proxy servers are used when you trigger the go command. Read more about GOPROXY in Module downloading and verification at golang.org.

  • GOSUMDB: identifies the name of the checksum database. The checksum database verifies that your packages from the go.sum file are trusted. Read more about GOSUMDB in Module authentication failures at golang.org.

  • GOPRIVATE: lists packages that are considered private. The go command does not use the GOPRIVATE or checksum database when downloading and validating these packages. Read more about GOPRIVATE in Module configuration for non-public modules at golang.org.

  • GONOPROXY: lists packages that are considered private. The go command does not use the proxy when downloading these packages. GONOPROXY overrides GOPRIVATE.

  • GONOSUMDB: lists packages that are considered private. The go command does not use the checksum database during validation of these packages. Overrides GOPRIVATE.

  • Other: any environment variable that you want to introduce. For example, you can introduce the GOMODCACHE environment variable that changes the default location of the Go modules cache from $GOPATH/pkg/mod to a user-defined location (for example, $WORK/modcache).

Introduce an environment variable in a project

  1. For a new project, click Go Modules in the New Project window.

    For existing projects, open settings by pressing Ctrl+Alt+S and navigate to Go | Go modules.

  2. In the Environment field, click the Browse icon at the end of the field.

  3. In the Environment variables window, click the Add button (the Add button) and select the template that you want to add.

    Introduce an environment variable in a new project

Get information about environment variable template

  • In the Environment variables window, click the Explain variable button (the Explain variable button).

    Introduce an environment variable in a new project

Installing Go SDK

Select a local copy of the Go SDK

Ensure that the provided path to the folder with Go SDK includes bin and src folders.

  1. In the New Project dialog, select Go.

  2. Click the Add SDK… button and select Local….

  3. In the file browser, navigate to the SDK version that is on your hard drive.

  4. Click Open.

Download the Go SDK

  1. In the New Project dialog, select Go.

  2. Click the Add SDK… button select Download….

  3. From the Version list, select the SDK version.

  4. In the Location field, specify the path for the SDK. To use a file browser, click the Browse icon the Browse icon.

  5. Click OK.

Productivity tips

Notify about replacements of local paths in go.mod file

Before you commit your changes, GoLand can show you a notification that you replaced local paths in the go.mod file. This might help you to avoid situations when these replacements are committed by mistake.

  1. Press Ctrl+K or select Git | Commit from the main menu.

  2. In the Commit tool window Alt+0, click the Show Commit Options icon (the Show Commit Options icon) and select the Analyze code checkbox. For more information about committing options, see Commit and push changes to Git repository.

    https://resources.jetbrains.com/help/img/idea/2021.3/go_notifications_about_changes_in_mod_file.png
    Gif