However, it's a good habit to organize your code as if you will publish itĮach module's path not only serves as an import path prefix for its packages,īut also indicates where the go command should look to download it.įor example, in order to download the module /x/tools,

A module can be defined locally without belonging to a repository. Note that you don't need to publish your code to a remote repository before youĬan build it. Of that directory, up to the next subdirectory containing another The directory containing its go.mod file as well as subdirectories Prefix for all packages within the module. Go.mod there declares the module path: the import path A Go repository typicallyĬontains only one module, located at the root of the repository.

Of related Go packages that are released together. Other source files within the same package.Ī repository contains one or more modules. Types, variables, and constants defined in one source file are visible to all Of source files in the same directory that are compiled together. The older, pre-modules version of this document, it is archived GO111MODULE environment variable is not set. Note: This document assumes that you are using Go 1.13 or later and the Module and introduces the go tool, the standard way toįetch, build, and install Go modules, packages, and commands. This document demonstrates the development of a simple Go package inside a

Install r package from github