How do I resolve "cannot find module for path X" importing a local Go module?

Question

In my Go project, I want to break out some generic functionality into a Go module, separate from the main project. I'm doing this outside of GOPATH in keeping with go's future. I don't want to publish the module on GitHub or anywhere else.

All my attempts to import this module into the main project result in:

cannot find module for path X 

I've run go mod init X in the module's folder. The contents of its go.mod file is:

module X 

Building or installing this module seems to do nothing. I've found no sign of it in $GOPATH/pgk/mod.

I've tried a variety of import statements:

• import "X"
• import "../x" (relative path to the module directory)
• import "../x/X" (path to the directory + module name)

Help!

Answer 1

So you wrote a Go "library" module X which:

• you don't want to publish on GitHub or elsewhere
• you want to import and use in your project (the "main" module).

Use a replace directive along with require

In your main module's go.mod, add the following lines:

require "X" v0.0.0 replace "X" v0.0.0 => "{local path to the X module}" 

The path should point to the root directory of X. It can be absolute or relative.

To import package util from module X:

import "X/util" 

(You don't import modules. You import packages from modules.)

---

Explanation

Go's module functionality is designed for publicly published modules. Normally, a module's name is both its unique identifier and the path to its public repo. When your go.mod declares a module dependency with the require directive, Go will automatically find and retrieve the specified version of the module at that path.

If, for example, your go.mod file contains require github.com/some/dependency v1.2.3, Go will retrieve the module from GitHub at that path. But if it contains require X v0.0.0, "X" isn't an actual path and you will get the error cannot find module for path X.

The replace directive allows you to specify a replacement path for a given module identifier and version. There are many reasons you'd want to do this, such as to test changes to a module before pushing them to the public repo. But you can also use it to bind a module identifier to local code you don't ever intend to publish.

More details in the Go Modules documentation:

• Can I work entirely outside of VCS on my local filesystem?
• When should I use the replace directive?

Hope this helps.

Answer 2

If you don't want to use Go modules, you don't need to. As of Go v1.13, by default, go modules are used. Therefore, you need to tell explicitly if you don't want to do this.

Example:

main.go:

package main  import (     "fmt"      "./pakk" )  func main() {     fmt.Println("Hello" + pakk.World()) } 

pakk/pakk.go:

package pakk  func World() string {     return " world" } 

In this case, running go run main.go will output

build command-line-arguments: cannot find module for path .../pakk 

but running

GO111MODULE=off go run main.go 

will output

Hello world